I recently got a computer back from repair and installed it in one of my DL3. I hooked the DL back into the network and I cannot see it in CMA. I have full control of the light from my console and I can see all my other DL3s. I am running the latest software for CMA that came out in November. Any ideas at what to look at.
There was a connectivity issue that came up due to a BETA build of software we sent out at one time. If that BETA build was loaded on the computer at any point, even if it is now on a different build of software, it can cause issues like you are seeing.
Basically, what happens is any time the unit runs on an auto-ip network (IP address of 169.254.x.x) the CMA connectivity will work fine. However, if the unit is run on a DHCP network, you will not see it in the CMA. This sounds pretty much like what you are seeing.
The fix, as strange as it is, is to plug the unit into a network that has an active internet connection and reboot the unit. Once it has booted, it should be fine to run under auto-ip again. It sounds strange, but it works.
We have a short write up on our website that details the problem here:
There was a connectivity issue that came up due to a BETA build of software we sent out at one time. If that BETA build was loaded on the computer at any point, even if it is now on a different build of software, it can cause issues like you are seeing.
Basically, what happens is any time the unit runs on an auto-ip network (IP address of 169.254.x.x) the CMA connectivity will work fine. However, if the unit is run on a DHCP network, you will not see it in the CMA. This sounds pretty much like what you are seeing.
The fix, as strange as it is, is to plug the unit into a network that has an active internet connection and reboot the unit. Once it has booted, it should be fine to run under auto-ip again. It sounds strange, but it works.
We have a short write up on our website that details the problem here:
