Today, I learned something the hard way. While most post on this blog are the result of research to meet an interesting challenge, today’s entry is the result of frustration. I was troubleshooting my SBS 2008 server, and while running a self test in Exchange 2007 I saw an error with IPV6.
I made the mistake not to do some research first. I was in a hurry to fix any problems present – last week, I’ve seen more computer / server / software probems than in the past 3 months – so I thought it would be a smart move to disable the protocol on our NIC. What damage could it do? I’ve yet to see IPV6 in action, so I assumed that if it wouldn’t help, it wouldn’t hurt either.
Don’t make that same mistake, my friends. Shortly after I disabled the IPV6 protocol, all hell broke loose. The Active Directory Services were failing; Exchange started failing, OWA started failing… I made another mistake by searching the solution in the wrong direction, and rebooted the server during the process.
Big mistake. The server got stuck during booting, on “Applying Computer Settings”. Apparently, that’s what an SBS Server does when you kill some of it’s most critical services. I quickly learned that disabling IPV6 on an SBS 2008 server is extremely dangerous.
Stopping IPV6 leads to multiple failing services, and will cause your server to hang during booting as a result
so, I had to re-enable IPV6. The fastest – and probably only – way was to boot the server into Safe Mode with networking services enabled. It’ll allow you to re-enable the protocol. Start the server again, and give it some time. Booting will take a few minutes longer than usual, but all your problems caused by disabling IPV6 should be fixed now.
Can you disable IPV6? Yes. Should you? Absolutely NOT
I’m kind of dissapointed in MS on this one. You’ve got to confirm every stupid action on your SBS 2008 server (“Do you REALLY want to add a printer?”), yet you can disable a crucial protocol with a single click, without being questioned. Ugh.