Ping Justification

Every day we are using our gadget that are really awesome. But what happens when the devices facing issue to communicate with the network.

Let's get started with the demonstration to troubleshoot the issue.

Today, I am going to describe the diagnostic ping command, or you can say it 'Justification of Ping result'

C:\>ping google.com

Pinging google.com [216.58.203.78] with 32 bytes of data:

Reply from 216.58.203.78: bytes=32 time=26ms TTL=55

Reply from 216.58.203.78: bytes=32 time=26ms TTL=55

Reply from 216.58.203.78: bytes=32 time=34ms TTL=55

Reply from 216.58.203.78: bytes=32 time=25ms TTL=55

Ping statistics for 216.58.203.78:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milliseconds:

    Minimum = 25ms, Maximum = 34ms, Average = 27ms

•    Pinging google.com: It resolving the google.com at 216.58.203.78 IP Address.
•  32 bytes of data: Means the size of the packet is 32 bytes sending to the google to check the communications are happening or not.

 * You can increase the size of the packet like this:

Windows:

Linux:

• Reply from 216.58.203.78: bytes=32

                Who is giving you the reply, and what size of the packet is receiving

• time=26ms

               Round trip time is 26 millisecond

               Means how many times it will take, the packet going through you system and returning back

               It is also used to say latency, you can check that, if we are pinging with the by default the 32 bytes has been applied and the result is showing 4 milliseconds.

And when we are pinging with the 65500 packet size it is showing that 74 milliseconds.  

It means the latency denoted the connectivity having utilization or not.

•  TTL=55

And the most impotent thing the TTL Value.

It is giving us the signature of the OS means TCP Stack is used on which type of systems.

• Windows: Default TTL is: 128

•  Linux/Unix: Default TTL is: 64

• Router/Switch: Default TTL is: 255

• Other Systems: Default TTL is: 99 (AVAYA IP OFFICE) or whatever they set on their Kernel.

If we are getting the nearest value of these TTL then we can easily guess that the OS.

Like now we are pinging the google.com and we are getting the 55 TTL value, it means the Google is using the Linux/Unix architecture based system.

Errors

• If we are getting Request time out, means the system is not active for the communication or the echo reply has been block by the firewall.
• Destination host unreachable, means the gateways having no route for the requested host.
• TTL Expired in Transit : As i mentioned earlier about the TTL, the packet can travel up to the default value of the originated  system
• It may the loop in your network.
• Hardware Error: A cable might be unplugged. Check the physical connections.

And most the important is :

1. Router send and receive a single request in 0.12 seconds.
2. System send and receive a single request in 1 second.

Justification By:

Naresh Mahato