Filter
Top Products
4-4
Double click on the server icon that has the question mark (?) on top. This
will cause NPort Server Lite Manager to reconnect with the server.
If the server is at a remote site:
1. Make sure the network connection to the remote site is okay. If no route
can be established to the remote device server, and you are connecting
through the Internet, you may need to wait until the route is
reestablished.
2. If the route is okay, try typing
ping [server-IP-address]
from your Windows host, where [server-IP-address] is the
device server’s IP address. If the device server cannot be pinged, you
will need to ask someone at the remote site to check if the power is on,
and make sure the connection is okay. After that, double click on the
device server icon that has the question mark (?) on top. This will cause
NPort Server Lite Manager to reconnect with the device server.
If the problem is still not fixed, contact Moxa technical support for further
information.
After rebooting my Windows host, why does one of my NPort Server Lite
device servers not appear when running NPort Server Lite Manager?
The problem might be that you have a DHCP server on your network. Since
DHCP servers can assign IP addresses to hosts connected to the network, the
IP address for either the host or NPort Server Lite might have changed. To
recover from this problem, you should:
1. Ask the administrator of your DHCP server to assign a dedicated IP
address to both your Windows host and to NPort Server Lite.
2. Make sure your NPort Server Lite Manager operating mode is set to
Custom.
3. Change the IP address of the server to the dedicated IP address assigned
by your DHCP administrator.
4. Change the IP address of your Windows host to the dedicated IP
address assigned by your DHCP administrator.
5. Modify the Security list to include your Windows host.Save the
Configuration.