Windows 10 IPv6 Ping and Traceroute returns from my router rather than target site

Copper Contributor

I'm enouctering a strange issue with ping and traceroute via IPv6 on serveral Windows 10 Pro 1909 machines on my network.


If I ping an external IPv6 host from one of the PCs the response appears to come back from my router based on the response time, rather than the host site. For example:



Pinging [2404:6800:4006:810::200e] with 32 bytes of data:
Reply from 2404:6800:4006:810::200e: time=1ms
Reply from 2404:6800:4006:810::200e: time<1ms
Reply from 2404:6800:4006:810::200e: time<1ms
Reply from 2404:6800:4006:810::200e: time=1ms

Ping statistics for 2404:6800:4006:810::200e:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Similarly if I attempt a traceroute it completes at my router after one hop (note have replaced my router address with example IPv6 address)

C:\>tracert -d

Tracing route to [2404:6800:4006:810::200e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2001:db8:1234:1::1

Trace complete.

 It makes no difference whether I use the FQDN or the IP address, or if the IP address is incorrect.


Other Windows 10 machines don't have the same issue and can ping and traceroute IPv6 hosts outside of my network.


I'm at a loss to explain why, and can't find any similar issues when searching online.

2 Replies

@adrianvesnaver just use the switch -4 ie. tracert -4 and it will return ip v4 addresses

@YH-ITprothat would be perfectly helpful if I was only wanting to do an IPv4 traceroute rather than IPv6. It seems to have resolved itself now any way.