Filter
Top Products
A-4 NPort Server Pro User’s Manual
¿ You cannot find the server after rebooting your Windows NT/95/98 server.
It’s possible that you have a DHCP server on your network. Since DHCP servers can assign IP
addresses, the IP address for either the host or NPort Server Pro might have been 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 NT/95/98 host and to NPort Server Pro.
2. Make sure your NPort Manager Pro operating mode is either Multi-Host or 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 NT/95/98 host to the dedicated IP address
assigned by your DHCP administrator.
. Note: Please refer to Appendix D to learn how to configure your Windows NT/95/98 to the
dedicated IP address.
5. Modify the Security list to include your NT/95/98 host.
6. Save Configuration.
Programming Problems
¿ Win32 COMM API functions return fail, or the PComm Pro library functions return a Fail
code - SIO_WIN32FAIL
The fail code for the COMM API functions implies something different than the fail code received
from the standard COM driver. For example, you get the fail code when the network connected to the
server is unreachable, or the server is offline. If the network connection is through the Internet, the
network could be unreachable if Internet traffic is jammed. This does not mean you have a defective
server. To recover from this type of error, you can modify your program so that the port is
automatically closed and then re-opened.
You should also check the following to make sure that the problem is only with the TCP/IP network:
1. If the server is off-line, turn it on.
2. If the route to NPort Server Pro is reachable, you may test it by using
Ping [NPort-Server-Pro-IP-address]
If a route to the server cannot be established, check your routing table or the server's
routing table.