On 12/05/2014 13:47, Mark Foster wrote:
Hello learned NZNOG-folks,
Many of you have been working hands-on with IPv6 a lot more than I have, so i'll ask this here.
In two cases, on two discrete systems, both Windows clients (one a Windows 7 workstation, the other a Windows 2008R2 server) a 'ping'[1] is run against a hostname.
In both cases a ping against a v6 IP address is tried (and failed, as the host has no v6 connectivity - and in at least one case, v6 is actually disabled in the network interface settings).
It seems likely that an automatic tunnel interface is up, most likely Teredo but possibly 6to4. You can see that with ipconfig /all or maybe better with netsh int ipv6 show int
A simple 'nslookup' check without specifying the query type returns both IPv6 and IPv4 responses for the hostname.
That's normal behaviour I believe. Brian
So why is the client trying to ping a v6 address when it has no v6 connectivity?
(and for the record, an answer of 'make v6 work' doesn't solve my problem, as much as it might be a simple resolution.)
Cheers Mark.
[1] as you can probably guess, ping isn't actually the end-use of this connectivity, but it was the first troubleshooting measure used. This is impacting on application-layer connectivity, so 'use-v4-only' ping syntax also doesn't help me. :-) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog