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?

Advertisements

3 Responses to “Changed Ping.exe output in Windows Server 2008?”

  1. Travis Says:

    What’s even more odd is that I’ve noticed that this happens ONLY to my Linux/Mac machines. It doesn’t happen to my Windows clients when I ping from my Server 2008 box.

    Still looking for a solution, because it doesn’t allow me to map drives to my W2k8 box from my Linux machines.

  2. Devan Says:

    I just ran across this myself and it’s causing havoc with my monitoring system. I happened only after I replaced my LINUX gateway (acting as a firewall) with a Juniper SRX firewall. My windows 2008 server where my altering software is running suddenly started returning host unreachable instead of request times out. My Vista laptop started the same behavior. It only happens when pinging down or non-existant hosts/IPs on the same subnet as the server. If I ping a down host or non-existant IP on a remote subnet I get the correct response (request timed out).

    Have you had any luck figuring out your problem?

  3. Kai Says:

    Hi Devan, I did attempt to fix anything — in my case I had full control over the monitoring system’s parser and patched it so that it recognises host unreachable as offline, too. In case you cannot modify that part, maybe talking to Microsoft Tech Support directly about this issue will help? Good luck!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: