0.00ms time reported

[GoogleCodeExporter]

A case was seen where paping reported 0.00ms on a 'problem' connection where it 
would sometimes connect and sometimes not.  I cannot give reproduction details 
because (a) this was performed by a 3rd party and (b) we don't know what is 
wrong the connection.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
a non-zero time period

What version of the product are you using? On what operating system?
v1.5.5 on Win XP

Please provide any additional information below.

Original issue reported on code.google.com by michael....@preciselyso.co.uk on 14 Dec 2011 at 3:03

[GoogleCodeExporter]

I saw this behavior when trying to ping and IP address which you don't have 
access to.

If you paping a URL and don't have a connection from memory you'll get 
something like 'Cannot Resolve Host'.  If you ping an IP you'll get 'Connection 
timed out' then at the end the summary will be 
min=0.00ms max=0.00ms average=0.00ms

This sounds like your 'issue'.

However, this value is arguably appropriate since it's a recognizable failure 
(who has a ping of 0ms in the real world?).

Perhaps the output of a failed ping could be just the (100% Loss) line instead.

Original comment by kelst...@gmail.com on 30 Sep 2012 at 8:30

[GoogleCodeExporter]

I have noticed on Windows systems that there is a form of rounding to the 
nearest 15.63 milliseconds. This means that if your roundtrip is less than 7 
millis it will be reported as 0.00ms. Try to connect somewhere further away and 
the timestamp will jump to 15.63 millis. Does anyone know how to get around 
this in Windows?

Original comment by HWJB...@gmail.com on 19 Jul 2013 at 11:10