This is a very peculiar problem with a station on our network. The client pc is running Windows 7 Pro. What makes this problem interesting is that this client is the only node on the network that seems to be experiencing this proglem. When I try to ping a specific Win 08 server by host name, I get an IPv6 address and get General failure. But when I ping it's IPv4 address, it responds just fine.
My first thought would check the DNS server the name resolutions to see what would be going on, but the problem begs the quesion, why does the station get an IPv6 address back and fails as opposed to using the IPv4 settings (which are static btw). What gives? I am including a screen shot of trying the one specific server and failing while trying another server with success. All other nodes on the network don't have problems communicating with the server the one station is having issues with. 
Answer
Found out through reading a couple of other posts that IPv6 is not exactly disabled by unchecking the protocal in the network adapter settings. Also, there's prefix policies built into windows that favors IPv6 over IPv4.
Turns out Microsoft has some tools that help with choosing presedence or choosing to disable IPv6 altogether on their site. Still not sure why I got the General Failure message in the first place, but at least I was able to fix the precedence using the Microsoft Fix it 50410 on that page (Prefer IPv4 over IPv6 in prefix policies).
No comments:
Post a Comment