Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
Solved

Posted on 2004-08-19
Medium Priority
244 Views
How can you tell if the statistics returned by a Ping command are good or bad.

For example I have 2 servers on the same network, one Linux one Windows 2000 that return different results.  I dont get any reuest time outs though.

0
Question by:Northumberland
[X]
###### Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

• Help others & share knowledge
• Earn cash & points
• 2
• 2

LVL 15

Expert Comment

ID: 11839715
Hi Northumberland,

If you could post some sample responses and we'll tell you what they mean :-)
0

LVL 9

Accepted Solution

Pentrix2 earned 1500 total points
ID: 11840708
A good average return is:

Reply from 192.168.1.1: bytes=32  time<1ms TTL=255
Reply from 192.168.1.1: bytes=32  time<1ms TTL=255
Reply from 192.168.1.1: bytes=32  time<1ms TTL=255
Reply from 192.168.1.1: bytes=32  time<1ms TTL=255

Ping  statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Mininum = 0ms, Maxinum = 0ms, Average = 0ms

The way to tell if it's a good return is notice the      time<1ms TTL = 255,  as long they return four consistently like the one above then it's good reply back.  It's common for several of the time<1ms TTL =255 to be a little off sometimes, but shouldn't too much.  If it does show different result every reply, then it's a slow connection causing it.  Notice the part that says:

Ping  statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4 Lost = 0 (0% Loss),

You want Lost = 0 (0% loss), this means all your packets that got sent did not slow down and get lost at anyway.
0

LVL 9

Expert Comment

ID: 11840713
I hope that was helpful and gives you a better understanding of a ping reply results.  :)
0

Author Comment

ID: 12607425
Pentrix2 - thanks for the info the ping stats are :

Pinging 192.168.1.38 with 32 bytes of data:

Request timed out.
Reply from 192.168.1.38: bytes=32 time=148ms TTL=127
Reply from 192.168.1.38: bytes=32 time=172ms TTL=127
Reply from 192.168.1.38: bytes=32 time=199ms TTL=127

Ping statistics for 192.168.1.38:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss
Approximate round trip times in milli-seconds:
Minimum = 148ms, Maximum = 199ms, Average = 173ms
0

LVL 15

Expert Comment

ID: 12614243
Northumberland,
Those are particularly bad response times.  On a LAN you'd expect to get a reliable sub-10ms

Are both machines on the same LAN and IP range?

Does this happen for all machines, or just one?
0

## Featured Post

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Sometimes you might need to configure routing based not only on destination IP address, but also on a combination of destination IP address (or hostname) and destination port number. I will describe a method how to accomplish this with free tools. …
The Need In an Active Directory enviroment, the PDC emulator provide time synchronization for the domain. This is important since Active Directory uses Kerberos for authentication.  By default, if the time difference between systems is off by more …
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…
###### Suggested Courses
Course of the Month11 days, 2 hours left to enroll