Many of us were disabling IPv6 protocol on a system, where it was not used. You can find many blog articles, where people are recommending disabling IPv6 (unfortunately the procedure in most of these articles is not correct).
Times are changing, and more organizations are preparing for IPv6 implementation. At iRangers we see this more often, especially on large-scale projects for government offices, banks, and other enterprise level companies.
Personally, I still prefer to have IPv4 protocol to be a default protocol on a task critical servers (by default, since Windows Vista IPv6 is a default protocol). So, here is a small trick on how to change the default TCP/IP protocol from IPv6 to IPv4. Execute the following command through command line or script:
%windir%\system32\REG.EXE ADD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents /t REG_DWORD /d 0x20 /f
I hope you find this trick useful. 🙂
Feel free to contact me, or any other Best IT Experts in Canada to discuss this or any other IT related challenges you have in your business. Don’t forget to subscribe to our news letter.
Right in your email inbox
Useful data from iRangers Experts
Subscribe to our mailing list and get interesting updates and tips.
Hello
Thanks for posting this article it is very helpful
What if I am not using IPv6 in our environment and have no plans to use IPv6 for the foreseeable feature.
can I simply un-tick the check box against IPv6 to it is not bound to the network card in the first instance ?
I have done this before on my Windows 10 computer when attached to a corporate network (Active Directory domain) and it appears to work OK,
I assume then, that un-ticking the check box for IPv6 is not the same as disabling the protocol ?
Thanks very much
Thanks for your question, unfortunately the answer is no. Unticking the box doesn’t disable IPv6 at all. Moreover, this is not a supported scenario by Microsoft. So technically speaking we’re all using IPv6 from Vista since 2006, and since then it’s a part of the network stack. So if you do not have any reason to disable it, just leave it alone. But if you do have weighty reason to disable it, just do it using our reg hack.
Cheers,
iRangers team
Hello I am attempting to run a Legacy game server (the game still has active servers online) everything is working fine except that when I try to connect Windows 10 keeps using the IPv6 to connect, as it is default/higher priority, and the game can only connect using IPv4. Others have been able to find ways to make it work however I find myself at a loss and unable to reprduce their methods. I have attempted several fixes but none seems to have any effect. Your post seems to indicate the same result as a method I have tried previously and I believe it should work, I am simply unable to get it right. I have used RegEdit to access the registry and tried to add the DisabledComponents information, but I seem to be missing something. If I can make it so IPv4 is preferred, either as a whole or just for certain processes, I believe I should be able to connect to my server without having to “disable” IPv6, since I know that is not recommended and I agree. Any help would be most appreciated and I would be able to help others with the same problem.
Thank you for your time