- This topic has 4 replies, 3 voices, and was last updated 2 months ago by
.
-
Posts
-
Hello,
Recently one of our MOMs have stopped connecting the to DAD over the network. We only get the red “status” light flashing.
We have quite a few ethernet jumps from the machine room to the studio, but no matter where we connected the MOM on the network the DAD didn’t identify the MOM.
Our network is PoE , but we also gave the MOM external power, and that didn’t help.
We have connected a spare MOM to the same ethernet cable, and that identified immediately.
I have scoured the manual for the MOM, but there’s not much other than it should just plug and play.
Have I missed anything before I go ahead and request for a replacement/repair? Is there a hard reset option on the MOM. Or a force identify on DAD?
Cheers.
I would also like help with this. I had my MOM setup with a static address on a network. Now I am on a different network and it does not show up on the device list. I can ping the MOM’s IP address.
Hi there,
We have seen this a few times in the past and although we cannot pin down a real issue, we have had some success with updating the network switches to handle the auto-discovery better. (We all rarely remember to update those Switch firmwares.)
Also, if you can try and connect the MOM to a single computer without any other network units on it, see if you can see the MOM show up and then check if the Network Settings are not clashing with an existing unit.
If this fails, then drop us a line on support@ntp.dk
Best,
JonHi Jon,
Thank you for your response. I figured it out. I tried to install dadman on another computer and it came right up. Turns out the security policy on the other computer was updated – probably firewall that prevented the MOM to be discovered. Thanks again!
- You must be logged in to reply to this topic.