Of course, the DNS server had two entries for all PCs which had Windows 7 as OS (also the server itself, Windows Server 2008 R2), one fro IPv4 and one for IPv6. XP users were pinging fine and returned IPv4 addresses and had no issues. It was only when pinging FROM server to CLIENTS I noticed that the IPv6 address was being looked for (but ONLY from Windows 7 Clients) even though we use IPv4 on the network, this resulted in failed packets. Tried everything I could think of including swapping cables, switch ports etc. We had users having intermittent access to the server. Was thinking my issue was something entirely different as we were experiencing network issues and then led me to the below: I can say that joined to domain versus not, may be a factor. If they ALL did it then I'd just say "Well that's Win7, not surprised MS is shoving ipv6 down my throat." but unfortunately not all Win7 endpoints have this happening. I wouldn't even have posted this except that I have seen some win 7 clients exhibit this behvaiour and others not. Neither of which I would trust not to cause other issues and neither of which is a conventional disable of this. In Win7 there's some registry items and of course the ability to completely disable the ipv6 protocol. The only solution I've had but it's only good for static clients, is to modify the hosts file.
get a localhost ping to return an ipv4 address. Don't worry about me or what YOU'D rather have happen, seek the challenge.
Most replies are "What's your problem?" and it's like look, if we are a technical community, judgement and self preference need a back seat here. Yeah that's a real pain in the ass and I still have yet to find a solution or someone who feels they would want to contribute.
0 kommentar(er)
