• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 259
  • Last Modified:

SBS 2003 takes hours to reboot

I have a client with a SBS 2003 server and every time i reboot the server it takes hours to reboot.  It becomes unavailable and unresponsive to pings after a min or so then sits dormant for half a day.  Any thoughts on what may be causing this?
0
aungelbach
Asked:
aungelbach
1 Solution
 
davorinCommented:
Any errors in event log? Maybe there is a problem with some service at startup.
Does in safe mode start normally?
0
 
aungelbachAuthor Commented:
not sure about safe mode, i work on this server remotely.  ill look at the log when it comes back up, its been rebooting for a few hours now and i need to get it up before tomorrow.
0
 
philetaylorCommented:
Very slow SBS startup can often be related to DNS settings as the server needs to be able to talk to a DNS server (itself). Check that the server IP address is listed as the first dns server (preferably the only dns server unless you have another domain controller)

 
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
aungelbachAuthor Commented:
would DNS make the server hang for 8 hours though?  it is still hanging and i rebooted it at 1pm today (9pm now).  i am trying to get a hold of the customer to go in and reboot it.
0
 
Shreedhar EtteCommented:
Hi,

Make the registry changes as per the http://support.microsoft.com/kb/827610

Hope this helps,
Shree
0
 
aungelbachAuthor Commented:
thanks but i understand the 10m exchange thing in SBS.  my problem isnt 10m, i rebooted the server 12 hours ago now and its still down.  you haveto manually push and hold the pwr button to get it to go down before it can restart.  i am looking for thoughts on what could be causing that.
0
 
aungelbachAuthor Commented:
i checked the server this morning and it only has one DNS entry which is itself.
0
 
aungelbachAuthor Commented:
Going through the server log after reboot this morning it seems that the server actually rebooted in a timely manner yesterday and was running all day but blocked all IP traffic.  Take a look at this entry and let me know what you think.

Source: IPSec    ID:   4292
The IPSec driver has entered Block mode. IPSec will discard all inbound and outbound TCP/IP network traffic that is not permitted by boot-time IPSec Policy exemptions. User Action: To restore full unsecured TCP/IP connectivity, disable the IPSec services, and then restart the computer.  For detailed troubleshooting information, review the events in the Security event log.
0
 
philetaylorCommented:
This indicates that your policy store may be corrupt. It can easily be rebuilt by following the instructions in this KB article http://support.microsoft.com/kb/912023

Cheers

Phil
0
 
aungelbachAuthor Commented:
I performed this registry operation and the server seems to be rebooting fine.  Thank you for your help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now