If you perform the registry change correctly, you'll get the ipv4 response.Īlright I disagree (you had to know this was coming) and before everyone goes ahead and down votes this comment into oblivion I do actually have a reason.įirst off I absolutely agree do not just 'uncheck IPv6' on your adapter. I've even seen Anti-V cause issues on servers after IPv6 has been un-chcked in the adapter.Įdit: for those asking for specifics, please see this reply:Ī quick and easy test to see if ipv6 is enabled or not is to ping localhost. Exchange, TMG, & SBS seems to be much more sensitive to this but just about any application can fall victim. Just because you're not feeling the pain does not mean something isn't mis-configured. I've worked with many many different customers over the past 6-7 years since this issues has become prevalent and trust me it's a bad idea. In most cases these are localized admins who really only work in one environment.
#CHECK FOR IPV6 ON MAC FULL#
And please if you do choose to disable it then do it the correct way I have listed above from Microsoft.Ī common excuse I hear from people is that "well I've always done it this way and never experienced issues so you are full of it".
/ChangeDNS-579e68143df78c3276990153-5c706b8e46e0fb0001f87cb7.jpg "check for ipv6 on mac")
Simply put, if you can't provide a good reason to disable it then DON'T (and ignorance is not a good reason). They disable it out of fear or because it's what someone else told them. Too many people when asked why they choose to disable it respond with silence. However, here's what I ask of you HAVE a reason to disable it. Now there may be environmental reasons why incompatible application, etc.
Microsoft states that they have no reason why IPv6 should ever be disabled and recommend it not be.
I've spoken with several people at Microsoft (Program Group, Premier Field Engineers, & Support Personnel) & their stance is the same. Now to follow up to that, I know there may be certain scenarios where IPv6 might need to be disabled but as for the official stance from Microsoft, here it goes. If you wish to disable IPv6 for whatever reason then simply follow the above articles and disable it via the registry (then reboot). If the protocol is unchecked on the adapter then the application is made largely unaware of this and can cause communications problems. In basic terms, your operating system is still utilizing IPv6 and so are the applications running on it.
#CHECK FOR IPV6 ON MAC WINDOWS#
Now here's several articles explaining why it is a bad idea to uncheck IPv6 on a Windows Adapter: So allow me to explain why.įirst off here's the post and the relevant comment. However, today I saw a post I had been commenting on updated detailing that this was likely the root cause. I've preached this many times sometimes on this subreddit and it seems to be a point of confrontation for some. Please DO NOT uncheck IPv6 on your windows network adapters. So because of this wide user base exposure I can confidently say I've seen this happen literally hundreds of times. I work in a services support & consulting role for a large IT company and deal with many different customers.
0 kommentar(er)
