OK, I just registered for this account to post in this thread...
Anyway, I'm having the same issue and wanted to share the info I've come accross regarding the particularly frustrating scenerio. Microsoft came out with an AutoConfiguration "script/program" in 98 that makes connecting to a network easier. This is prior to the introduction of DHCP and became the alternate method when a DHPC server is not available. It is now the primary means of accessing a network connection via IPv6. The AutoConfig will search and assign an IP based on the local network. I've come accross the option of dissabling AutoConfiguration in the registry, but there has to be an easier way.. I hope. As of this post the only reason disabling IPv6 should work can be found here:
http://www.microsoft.com/technet/com...uy/cg1005.mspx
"
Note: Due to misconfigured DNS servers on the Internet, computers that use both IPv4 and IPv6 might not be able to resolve names and connect to Internet resources. This rare problem occurs when a misconfigured DNS server receives a request to resolve a name to one or more IPv6 addresses (a request for AAAA records). If the DNS server does not support IPv6, the name query fails. The querying node then sends a request to resolve the name to a set of IPv4 addresses (a request for A records). The misconfigured DNS server drops the subsequent DNS query for IPv4 addresses and the entire name resolution attempt fails, resulting in impaired network connectivity for the requesting node. If you are experiencing this problem, ask your Internet service provider to reconfigure their DNS server to accept the subsequent DNS query for A records after failing the DNS query for AAAA records. Alternately, you can temporarily disable IPv6 on the requesting computer. This issue exists on the DNS servers and is common to all computers that use both IPv4 and IPv6."
I just disabled my IPv6 connection and the "Preferred" connection reverted back to my previous static Ip address. Awesome!
Once everyone begins to move over to v6, we should be seeing less of this issue.
Hope the info helps.