Ok,

if noone likes 'TLL=' I explain it more to the point and hopefully everyone will agree that it is the only way :

So, assuming you run Windows NT Workstation, how would you ever get a valid response in finding '0% loss' (there is never ever such a phrase on Console !)

sample :

quote:
C:\WINNT\system32>ping 10.128.12.20

Pinging 10.128.12.20 with 32 bytes of data:

Reply from 10.128.12.20: bytes=32 time=10ms TTL=125
Reply from 10.128.12.20: bytes=32 time<10ms TTL=125
Reply from 10.128.12.20: bytes=32 time<10ms TTL=125
Reply from 10.128.12.20: bytes=32 time<10ms TTL=125

C:\WINNT\system32>
(Have you noticed that there is "TTL=" in every reply ???)

Good, and now for guys trying to search for "TTL" which CAN also result in erroneous response !

Here is the CAN case :

quote:
C:\WINNT\system32>ping 10.134.126.20

Pinging 10.134.126.20 with 32 bytes of data:

Reply from 10.63.4.133: TTL expired in transit.
Reply from 10.63.4.133: TTL expired in transit.
Reply from 10.63.4.133: TTL expired in transit.
Reply from 10.63.4.133: TTL expired in transit.
As you might see there is in fact a TTL to be found but that doesn't mean that you get reply from the machine you pinged !

so 'TTL=' is it (for any MS OS you can imagine !)

[Mad]

{edit}Oh yeah ! 'Request timed out' is also nonsense :

quote:
C:\WINNT\system32>ping xyz
Bad IP address xyz.
would return 'reply' [Roll Eyes]
{/edit}

[ 19. March 2003, 09:32: Message edited by: jpols ]
_________________________