User`s guide

545
Troubleshooting the LAN Connection
Troubleshooting the Initial Connection
• Error Messages
If error messages appear, then check the command syntax before
continuing with the troubleshooting. If the syntax is correct, then resolve
the error messages using your NFS documentation.
Certain NFS software packages permit the use of hostname in place of the
IP address. In this case, if an unknown host error message appears, then
check the node names database to see that the hostname and IP address
are correctly entered.
Refer to your NFS documentation for specific information on any error
messages.
•No response
No packets received indicates no response from a ping.
If there is no response, type in the IP address with the ping command.
Check that the typed address matches the IPaddress assigned in the LAN
Settings menu, then check the other addresses in the menu.
Check that the hostname and IP address are correctly entered in the node
names database and that the IP address matches the IP address assigned
in the LAN Settings menu.
If the logic analyzer still does not respond to ping, then the problem is
possibly in the logic analyzer hardware. To check the logic analyzer, refer
to "Verify the logic analyzer performance" in this chapter.
• Intermittent Response
On a multiclient network, receiving 1 to 8 packets indicates a problem with
the network. Because the number of packets received depends on your
network traffic and integrity, the number might be different for your
network.
Use a LAN analyzer or LAN management software to monitor activity and
determine where bottlenecks or other problems are occurring. The logic
analyzer still functions, but communications over the LAN will be slower.
On a single-client/single-server network, the most likely cause of
intermittent response to an echo request is a hardware problem with the
LAN module installed in the PC, the cable, or the logic analyzer. To check
the logic analyzer, refer to "Verify the logic analyzer performance" in this
chapter.