Agilent Technologies PSA Series User And Programming Manual page 329

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 host name. Check that the typed
address matches the IP address assigned in the
menu, then check the other addresses in the menu.
Check that the host name 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 instrument, starting with
the your workstation. Ping each gateway, then attempt a ping of the
remote file server.
If the instrument still does not respond to ping, then you should
suspect a hardware problem with the instrument. To check the
instrument performance, refer to "Verify the Instrument
Performance" in this chapter.
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 instrument 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 instrument. To
check the instrument, refer to "Verify the Instrument Performance"
later in this chapter.
The Standard UNIX PING Command
host [packetsize] [count]
Description The ping command sends an echo request packet to the host
once per second. Each echo response packet that is returned is listed on the
screen, along with the round-trip time of the echo request and echo response.
Chapter 5
Programming Fundamentals
Using the LAN to Control the Instrument
System, Config I/O
Synopsis ping [-r] [-v] [-o]
329