Filter
Top Products
8-6 LAN Interface Supplement
General Troubleshooting
Troubleshooting the Initial Connection
No Response
No packets received indicates no response from a ping.
• If there is no response, try typing in the IP address with the ping
command, instead of using the hostname. Check that the typed
address matches the IP address assigned in the
menu, then check the other addresses in the menu.
• Check that the hostname and IP address are correctly entered in the
node names database.
• If you are using a UNIX environment, ping each node along the route
between your workstation and the analyzer, starting with the your
workstation. Ping each gateway, then attempt a ping of the remote
file server.
• If the analyzer still does not respond to ping, then you should suspect
a hardware problem with the analyzer. To check the analyzer
performance, refer to the analyzer’s Service Guide.
• Make sure that you have used the appropriate cable to connect your
analyzer to the LAN. A patch cable can be used to connect your
analyzer to a hub, or a cross-over cable can be used for direct
analyzer–PC links.
Intermittent Response
If you received 1 to 8 packets back, there is probably 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
analyzer will still function, 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 analyzer. To check the
analyzer performance, refer to the analyzer’s Service Guide.
LAN Port Setup