The ping command, when using computername, doesn't include "TTL=" even though it is successful - which is a new behaviour on me.
It does include TTL= when using the IPV4 IP address in the ping command but not with IPV6 IP address
Maybe this is an IPV6 change - I haven't tested it much - but if so then I fear it breaks some common ping code
Tested in Windows 8.1 32 bit.
Code: Select all
c:\>ping localhost
Pinging PC [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Code: Select all
c:\>ping PC
Pinging PC [fe80::a15:b08:f88f:a5e2%3] with 32 bytes of data:
Reply from fe80::a15:b08:f88f:a5e2%3: time<1ms
Reply from fe80::a15:b08:f88f:a5e2%3: time<1ms
Reply from fe80::a15:b08:f88f:a5e2%3: time<1ms
Reply from fe80::a15:b08:f88f:a5e2%3: time<1ms
Ping statistics for fe80::a15:b08:f88f:a5e2%3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
With IPV4 address:
Code: Select all
c:\>ping 192.168.1.03
Pinging 192.168.1.03 with 32 bytes of data:
Reply from 192.168.1.03: bytes=32 time<1ms TTL=128
Reply from 192.168.1.03: bytes=32 time<1ms TTL=128
Reply from 192.168.1.03: bytes=32 time<1ms TTL=128
Reply from 192.168.1.03: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.03:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms