Jharrisonsnbs
asked on
Disable IPv6 on Windows Server 2012
Hello, I have a Windows 2012 server that I would like to disable, or not use IPv6 on. The server is the acting Domain Controller. When I uncheck IPv6 in the network settings, under the DNS panel for Reverse lookup zones, the server is unable to resolve itself as a nameserver. I used to be able to uncheck IPv6 and modify the "disabledcomponents" registry key in windows 2008 R2 to essentially remove IPv6 from my internal network. I did check and all of the IPv4 records for the server are in DNS. I don't have a DHCP scope or range for IPv6 configured internally, because I would prefer to not use it.
Any advice would be greatly appreciated. I've been looking online and haven't found much on this topic that pertains to my situation.
This was the article I used to follow for my 2008 R2 servers http://support.microsoft.com/kb/929852
I wouldn't mind if it was still enabled, just not active. The issue before was IPv6 caused communication problems between my servers and the only fix was to turn it off. I have read a few articles claiming that if you turn IPv6 off in 2012, it will cause core issues with the server.
Thank you!
Any advice would be greatly appreciated. I've been looking online and haven't found much on this topic that pertains to my situation.
This was the article I used to follow for my 2008 R2 servers http://support.microsoft.com/kb/929852
I wouldn't mind if it was still enabled, just not active. The issue before was IPv6 caused communication problems between my servers and the only fix was to turn it off. I have read a few articles claiming that if you turn IPv6 off in 2012, it will cause core issues with the server.
Thank you!
Rob Williams
You should be able to disable it in the same way (registry key and NIC IPv6 properties), but it is definitely not recommended on a 2012 or newer DC , or Exchange 2010 or newer. Also I would not disable on any version of SBS or Essentials. Perhaps it would be better to look into the "communication problems". IPv6 has been around since server 2000 and the bugs ironed out since server 2003 SP2. It should not be a problem to just leave it in its default state. No need to set up DHCP scopes or configure.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I followed the old steps I used on the 2008 servers. The DNS did appear to work and was able to resolve the reverse lookup zone. I'm probably taking a risk on the server, but if the only function it is serving is DC, I can always stand up another one.
@jharrisonsnbs, Do you remember running into any trouble after you disabled IPv6? Did you then remove it from the DHCP? Did you then remove it from DNS? Anywhere else? Would you do it again?
Thanks,
B.
Thanks,
B.