I have a question (and maybe this is the designed behavior). We have quite a few new Windows 7 clients that we didn't have in the past. They are experiencing "slowness" issues communicating with 2008 Servers. I've been doing some digging and it appears that all the Windows 7 PC's are attempting to talk to 2008 Servers via 6to4 rather than through the IPv4 addressing. It seems many times they can't actually communicate via the DNS resolved 6to4 addressing and eventually fail back to using IPv4. (At least I think this is what's happening but, it's taking upwards of 30 seconds for that to happen). Obviously this is causing issues. If I disable the 6to4 tunnel on the 2008 boxes, and then delete the nasty DNS entries that contain the 6to4 IPv6 2002:: addressing, the clients are happy and they talk IPv4 no delay. Thoughts?
Here is an example also, no difference between the two clients short of the two destinations being on different VLAN's (since it's using the 6to4 I'm assuming it should be getting converted back to IPv4 and vice versa at the end-points) I'm really wondering why the 6to4 address is ending up in DNS as the chosen addressing...
Pinging test-example [2002:95d0:2c90::95d0:2c90] wit h 32 bytes of data:
Reply from 2002:95d0:2c90::95d0:2c90: time<1ms Reply from 2002:95d0:2c90::95d0:2c90: time<1ms Reply from 2002:95d0:2c90::95d0:2c90: time<1ms
Ping statistics for 2002:95d0:2c90::95d0:2c90: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging test-example2 [2002:95d0:338f::95d0:338f] wi th 32 bytes of data:
This isn't really an MS support forum but I'll have a stab at it. Windows >= Vista prefers IPv6 over IPv4 and will try to use it as much as it can. Even in a basic Windows domain setup, the client and the server will communicate using the link-local IPv6 addresses and the netlogon service will register whatever IPv6 addresses the server has in DNS.
Did you enable 6to4 on the server? The easiest fix will probably be to disable any 6to4 adaptors in Device Manager and restart the netlogon service.
If your Windows 7 clients get public IP addresses they can and will use 6to4 if possible. This is mostly due to the fact how the clients are configured. The server has no control what protocol your clients may use if they have the option of using either IPv6 or IPv4.
Thus, disable IPv6 on your Windows 7 clients. That will get rid of this problem altogether.
Otherwise, if you don't want to use 6to4 (which isn't a good idea anyway unless you trust whoever is operating the anycast address 220.127.116.11) disable it on the clients. They shouldn't use the 6to4 unless you trust the 6to4 relay.
Same thing may apply to the teredo tunnel.
Otherwise, register for a public IPv6 address space and set it up in your LAN. Then all your clients will get normal IPv6 addresses and again, this should fix your problems. This should be the way to go eventually. Sooner or later you'll need IPv6 support in your network, thus why not start now?
You could of course use netsh on your clients to configure protocol preferences. If you don't like clients to register their IPv6 6to4 address in your DNS server, disable the DDNS update in the network properties.
Windows Vista, 2008 and Windows 7 are all pushing hard to enable IPv6 use by default where possible. There are bumps in the transition process, as you have noticed.
The best answer is to enable IPv6 on your network infrastructure, but failing that you can disable elements of IPv6 per the Microsoft Knowledge Base article at http://support.microsoft.com/kb/929852. Otherwise, you can alter the prefix policy to reflect what you'd like to see happen.
There has been a lot of writing about what the "prefix policy" should be and whether 6to4 is preferred over IPv4.