• State Not Answered
  • Date
    stephenwyker
  • Date
  • Replies 17 replies
  • Subscribers 6 subscribers
  • Views 2744 views
  • Users 0 members are here
Options
Related

Lose of CMA conectivity

V1.5.4

Last night I could not connect to my axon from my normal PC (which is dedicated to this use, with no internet access) -- I tried another PC, and a mac with no luck .. it never showed up. Direct cable, auto assigned IP. I tried putting it on a router, my laptop got the IP, as did the AXON. I then booted with the local CMA, and it would "see" it but then said something like "could not connect to remote"

This has happened 2 or 3 times before (and it always seems to sense when I'm in a hurry and don't have time to screw around) -- Any idea what could cause that?

It play back media normally, with no issues. I only have a small amount of custom content on the device.
Parents
  • 0
    Stephen...

    I had this happen recently also. Here is the thread along with Matt's response of what helped.

    forums.highend.com/showthread.php?t=9089


    There was a BETA build of software that went out sometime last year (b1704) that has caused some serious problems with CMA communication in conjunction with a DHCP network. Basically, any DL/Axon server that was upgraded to 1704, and then to any other version of software will have issues communicating with the CMA when running under DHCP.

    To be sure this is the issue, can you change your ArtNet settings in the DP8000 to run in the 169.254.x.x range, and then take the DHCP router out of the network? At least temporarily to test. If you do this and you get all of your DLs back in the network, then this is the issue you are running into.

    The best way we have found to fix it (and bear with me here, it will sound strange) is to plug the router back into the network, connect an active internet connection into the router, then reboot the DL/Axons servers and allow them to fully boot. Once they come back up, you should see them all in the CMA. As long as they are back in the network at this point, the problem will be permanently cured.


    I know it sounds weird, but it worked for me.
Reply
  • 0
    Stephen...

    I had this happen recently also. Here is the thread along with Matt's response of what helped.

    forums.highend.com/showthread.php?t=9089


    There was a BETA build of software that went out sometime last year (b1704) that has caused some serious problems with CMA communication in conjunction with a DHCP network. Basically, any DL/Axon server that was upgraded to 1704, and then to any other version of software will have issues communicating with the CMA when running under DHCP.

    To be sure this is the issue, can you change your ArtNet settings in the DP8000 to run in the 169.254.x.x range, and then take the DHCP router out of the network? At least temporarily to test. If you do this and you get all of your DLs back in the network, then this is the issue you are running into.

    The best way we have found to fix it (and bear with me here, it will sound strange) is to plug the router back into the network, connect an active internet connection into the router, then reboot the DL/Axons servers and allow them to fully boot. Once they come back up, you should see them all in the CMA. As long as they are back in the network at this point, the problem will be permanently cured.


    I know it sounds weird, but it worked for me.
Children
No Data

www.etcconnect.com