none
I am having real issues with IPv6 components - can I completely remove them?

    Question

  • Hello,

    I have a small network that uses Server 2012 to host a variety of Virtual Machines (mix of 2k8 and 2k12).  We have been having intermittent issues with IPv6 entries for a number of our production machines showing up in our DNS, which causes multiple issues with our experience on the network.

    I have attempted to "uncheck" IPv6 on the network device, but this does not seem to work - what happens is that a "tunnel adapter" is created (a 6-to-4 type) which gets itself an IPv6 address, which in turn shows up in DNS and makes problems.

    I have found the 6-to-4 adapter in the Device Manager and uninstalled it, but that only works for so long - it appears that at random intervals (may or may not be related to monthly patching), it will show back up on its own, and go back to causing trouble.

    Higher authority has dictated we not use IPv6 functionality, so we cannot integrate it in to our daily operations.

    Is there a way to completely and utterly remove IPv6 functionality so that none of these "rogue" adapters can keep giving me grief?

    I asked this over at the Server 2012 forum earlier (https://social.technet.microsoft.com/Forums/windowsserver/en-US/960be749-14fe-4d07-9bcf-3393ede8af32/i-am-having-real-issues-with-ipv6-components-can-i-completely-remove-them?forum=winserver8gen) and they suggested I come here.

    The issue seems to be that disabling or uninstalling 6-to-4 adapters doesn't work long, as they always come back online at some point in the near future, and my DNS server stops listing the IPv4 address in favor of this 6-to-4 setting.

    Thanks,

    M.

    Tuesday, September 12, 2017 2:43 PM

All replies

  • Hi,
    You can disable IPv6 on the host computer through the DisabledComponents registry value(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\). The DisabledComponents registry value affects all network interfaces on the host.

    Important :Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

    More detailed information about how to disable IPV6,  please refer to the following article:

    https://support.microsoft.com/en-us/help/929852/how-to-disable-ipv6-or-its-components-in-windows

    Best Regards,

    Frank



    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Wednesday, September 13, 2017 6:26 AM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 19, 2017 4:12 PM
  • Hello Frank,

    In setting that registry key, would that prevent Windows itself from re-enabling it?  We have been able to deactivate it manually (without a reg key change) but the issue seems to be either during a reboot (and not consistently) or during patching, the IPv6 6-to-4 adapter turns itself back on.

    Thanks,

    M.

    Tuesday, September 19, 2017 4:15 PM
  • Hi,

    In my test environment, rebooting doesn't enable ipv6.


    Best Regards,

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, September 20, 2017 9:45 AM
  • Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,
    Frank

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 03, 2017 9:21 AM