Archive for June, 2009

Changed Ping.exe output in Windows Server 2008?

2009-06-04

Do I see this right that output of ping.exe has changed for a system that is unreachable between Windows 5.2 (Windows Server 2003) and 6.0 (Windows Server 2008)?

On the older Windows versions pinging a system that is offline would give output such as this:

Pinging 192.168.0.228 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.228:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

So anyone who is calling ping from a wrapper and parses the output — not saying it’s a great idea — would then probably look for “timed out” or “(100% loss)” to conclude there is a problem. Or finding “(0% loss)” would indicate all is well.

Doing a similar test several times on Windows 2008, the result will look like this after a minute or so:

Pinging 192.168.0.228 with 32 bytes of data:
Reply from 192.168.0.94: Destination host unreachable.
Reply from 192.168.0.94: Destination host unreachable.
Reply from 192.168.0.94: Destination host unreachable.
Reply from 192.168.0.94: Destination host unreachable.

Ping statistics for 192.168.0.228:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

See how it has changed? The host 192.168.0.94 is the source machine pinging, not the ping target. The “Request timed out” is gone, the “(100% loss)” is gone, and instead ping returns “(0% loss)” — which previously was only printed out when the target host was indeed reachable.

The ping statistics show full success, counting the “Destination host unreachable” replies as good replies. Interesting!

Any comments? (apart from parsing ping’s output is not a good idea anyway) How is it on Vista and Windows Seven?