Table of Contents
Advertisement
• Reply from <IP address> - the host IP number that
responded.
• bytes=32 - number of bytes sent in the packet.
• time=280ms - time (in milliseconds) of the round trip to
the host, which gives an indication of the quality of the
communications link. The time taken for a packet to
reach the host is also called 'latency'. Depending upon
the location of the remote host, a good time would be
less than 100 ms (i.e. 1 second). A variation in the times,
called 'jitter', may indicate poor communication with
the host.
• TTL=46 - Time To Live. Indicates the hops along the
way. Every ping packet that is sent out has a TTL value
which by default is 255. For every router hop that the
packet passes through, the TTL figure gets decreased by
one. So in the example above the TTL of 46 means (255
- 46) 209 hops. Variations in the TTL show that the
packets are traversing different routes.
• Packets sent - total number of packets sent during the
test.
• Packets received - number of packets received by the
host. A successful 'ping' receives back the same number
of packets that were sent. Failure to receive back any
packets indicates a communications path does not exist
between sender and recipient.
• Packets lost - number of packets not received (i.e. lost
on the way). Loss of some packets may indicate that the
communications link requires troubleshooting.
An unsuccessful 'ping' may display:
• Request timed out - means there was no response in the
default time period of one second. If the latency of the
response is more than one second, try using the -w option
on the ping command to increase the time-out, e.g. try
ping -w 5000 [IP address] to allow responses within 5
seconds.
• Unknown host - means that the IP address does not
exist.
• Destination host unreachable - means that the IP
address is recognised but cannot be reached.
46
Basic operations
Ping options
• -a - resolve Address to hostname.
• -f - set "Don't fragment Flag" in packet.
• -i - Time To Live (TTL).
• -j - host-list loose source route along host-list.
• -k - host-list strict source route along host-list.
• -l - size send buffer size.
• -n - count Number of echo requests to send.
• -r - count Record route for count hops
• -s - count timestamp for count hops.
• -t - pings the specified host until interrupted.
• -v - Type Of Service (TOS).
• -w - timeout (in milliseconds) to wait for each reply.
Ping Commands
• Ctrl + Break - to see statistics and continue.
• Ctrl + C - stop ping.
• > c:\filename.txt - send results to a text file.
Ping the loopback address - type ping
127.0.0.1
Successfully pinging the loopback address verifies that
TCP/IP is both installed and configured correctly on the
local client. If your loopback test fails, then it means IP
stack is not answering. If any TCP drivers get corrupted, or
if your network adapter is not functioning properly, or if
any of the other service is interrupting IP, then lack of
response might can occur. Open event viewer, and look for
problems reported by setup or by the TCP/IP service.
Ping the local client - ping <IP address>
Successfully pinging the local client's IP address verifies
that the client was successfully added to your network. If
you cannot successfully ping the local IP address after
successfully pinging the loopback address, check that the
local client's IP address is a valid IP address, check the
routing table, and check network adapter driver.
Ping the default gateway - ping <IP
address>
Successfully pinging the default gateway of the local client
verifies that you can properly communicate with the local
subnet to your local host and your default gateway is also
functioning properly. If you cannot successfully ping the
default gateway after successfully pinging the local client,
check the default gateway.
Advertisement
Table of Contents
