Weird, IP6 is dual stack so should not cause an issue like this unless their are incorrect IP6 DNS records taking presidence. Did you try a tracert hostname to see where it was trying to go and a nslookup hostname to see what the DNS server was pushing out?
Originally Posted by Duke5A
No I didn't, but now I'm wishing I did. I've only ever seen this happen this one time and we were in the middle of imaging a couple hundred netbooks while running them on batteries (quite the undertaking, think D Day). After a reboot and no fix with everything running on batteries I was in a hurry to make the problem go away.
Originally Posted by SYNACK