Found ENET-9481 but can't connect, not at expected IP address

[Brett_Percy]

I have a NI ENET-9481 device at a remote site that I can't get to connect in MAX.  There was previously another ENET-9481 running there for several months before it apparently failed.

The new device was set to static IP address 192.168.0.5 before it was shipped to the remote site, then just plugged in as a replacement for an existing ENET-9481 that had failed.

The device initially showed up as disconnected, although the Device Information showed up.  After trying to reconnect the device, I changed the last octet of the address to 55 in MAX, and MAX reported that it couldn't access the device.  This seemed reasonable as it wasn't connected to it.

I then deleted the device and attempted to re-add it by searching for new devices on the network, reasoning that the existing device in MAX might have been a 'ghost' of the previous ENET module. MAX found the device, not at the correct IP address (192.168.0.5) but at the changed address (192.168.0.55), even though MAX reported that it was not connected and that it couldn't communicate with the device.  Although the device was found, it could not be connected to.  I removed and re-added the device a couple of times, restarting MAX on the off chance it might help

I then removed the MAX database at C:\Documents and Settings\All Users\Application Data\National Instruments\MAX as per this KB article: http://digital.ni.com/public.nsf/websearch/BECA7EF547AE755386256CC600789C8B?OpenDocument

After rebooting the machine, I still get the same result.

I tried pinging 192.168.0.5, and I get a response.  I also succesfully telneted to port 80 at this address, and tried to GET index.html.  This returned an error page from 'Mbedthis-Appweb/2.4.0', so assume this means it's the ENET-9481 and not a Windows PC squatting on its IP address.

I also tried pinging 192.168.0.55 but I get no response, so I guess there is not device actually at that address.

[Brett_Percy · Accepted solution]

For the benefit of anyone who stumbles across this - The problem seems to have resolved itself;  the power to the ENET-9481 was cycled and it came up working,  with the changed IP address (192.168.0.55)