I have to admit, out of all server installs I have ever done, I have probably had one of the worst experiences ever recently with 2008 SBS.
I thought I would blog about this problem simply because I was in a mess and I'm sure anyone else in this scenario would want to get out of it just as quickly as I did!
My Scenario
At first the clients were complaining that the Exchange was down, I noticed that the store service wasnt running so quite rightly I tried to start it but it wasnt having any of it. I went to Event Viewer and it had items like "Cannot connect to Active Directory" and "Exchange topology not starting" amongst many others. My most stupid mistake at this point was to reboot the server which is where I ended up watching a spinning wheel at "Applying Computer Settings".
I couldnt think what it was until I found that it could be affected by IPv6 at which point it became clear that this definately was the problem, I had turned it off the day prior to troubleshoot a vista application issue.
I found one fix on the net but it didnt help my situation unfortunately, it may still work for others though. You simply go into the registry and navigate to the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
a.In the Edit menu, point to New, and then click DWORD (32-bit) Value.
b. Type DisabledComponents, and then press ENTER.
c. Double-click DisabledComponents.
5.Enter "ffffffff" (eight f’s), and then click OK.
My Resolution
So I rebooted into Safe Mode with Networking and logged on as the Domain Administrator (The first time it told me there were no logon servers available to service my request) I tried again and it was fine!
Go into Network and Sharing Centre, Manage Network Connections, Go to Properties on the connection and tick IPv6.
You can then reboot the machine and it will boot up ok. (I will also add that it looked like it wasnt going to work, it still spun around applying personal settings for around 3 minutes before it booted so be patient.)
Good luck to anyone else who gets this problem and I hope the above helps!
Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!
Subscribe to:
Post Comments (Atom)
Bulk discount code 2022 - 35% Off First Order Discount Code at bulk.com
Bulk.com / Bulk Ltd - First Order Discount Code! Get 35% off of your first order at Bulk, home of award-winning Sports Supplements, high ...
Don't disable Ipv6 on a SBS box. Exchange needs it.
ReplyDeletei have this problem and cant exit this.... i dont know the static ipv6 after tick it
ReplyDeleteThank you so much for this, it saved me hours of head scratching at 3AM!
ReplyDeleteThis is the exact problem I'm having. I'm running on a VMWare box and was just about to provision another machine and start again from scratch when I thought I'd have a search. When I read your blog it was like manna from heaven. Thank you SO much
ReplyDeletedidn't do the trick for me :(
ReplyDeletelook at this :
ReplyDeletehttp://blogs.technet.com/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx
Thanku thanku thanku!!!
ReplyDeleteThank you for your post. This just fixed our SBS boot issue!
ReplyDeleteI know this post is almost a year old...But I had to say that this saved my bacon today. Long live the internet and the information shared by people!
ReplyDeleteHoly cow You just saved me DAYS!
ReplyDeleteI had one server we ended up replacing the MB on and it just happened to another one and I finally found this!
Note NEVER turn off IPV6!
Thanks so much again!!
Hats off to you sir!
ReplyDeleteSBS2008 is such a pile of crap that IPV6 disabling can leave it in such a dribbly mess.
ReplyDeleteMicrosoft strikes again!
Fantastic, worked for me also. Thanks for taking the time to post this!
ReplyDeleteSaved me hours.
Jason
Hey kris , i dont know if this is the right place to post, but i have issues with SBS 2008 exchange 2007 server ,
ReplyDeleteIn the event viewer im recieving every 15min the following
Process MAD.EXE (PID=1348). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers
dont know what to do
Help !!
Ssweeet man, that fixed it for me, I removed the tick cos of nslookup errors the other day and forgot I had done it then rebooted and bam the circle of death!! Saved my ass, Thanks for posting this champ..
ReplyDeletethis is light and cool blog... enjoyed while reading this . haha :)
ReplyDeletewell SBS 2008 is the cool server and when i was working on it i didn't face any prob but thinking that it would save me from the future prob..
Thanks for this, this helped greatly.
ReplyDeleteFor anyone getting stuck logging in to safe mode with networking follow below: -
1. click switch user.
2. login as different user.
3. User domain\username (without the .local.)
Safe mode tries to default to .local but fails to login with this.
We couldn't access .co.uk websites so our ISP suggested turning of IPv6. Got to work on Monday morning to find this exact problem. Thank you so much.
ReplyDeleteI registered just to say thank you. I was seconds away from rolling back to the previous night's backup (a 1.5TB restore) when I found this. You saved my arse, and accelerated a virtualization project that was slated for the end of this year.
ReplyDeleteThanks a lot!! This helped me out!
ReplyDeleteThanks very much,this tip just saved me hours !!!!!
ReplyDeleteThe article is still helping out! Same issue for me after I thought I was doing a service by "cleaning up" a server by getting rid of stuff it didn't need. Two days later when it rebooted, it wouldn't load the OS properly...I should know better too...I've been doing SBS servers for years now. Brain fart!
ReplyDeleteThank you Kris, you saved my bacon!!! :)
ReplyDeleteNice post.
ReplyDelete