Link to home
Start Free TrialLog in
Avatar of aungelbach
aungelbachFlag for United States of America

asked on

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?
Avatar of davorin
davorin
Flag of Slovenia image

Any errors in event log? Maybe there is a problem with some service at startup.
Does in safe mode start normally?
Avatar of aungelbach

ASKER

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.
Avatar of philetaylor
philetaylor

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)

 
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.
Hi,

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

Hope this helps,
Shree
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.
i checked the server this morning and it only has one DNS entry which is itself.
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.
ASKER CERTIFIED SOLUTION
Avatar of philetaylor
philetaylor

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I performed this registry operation and the server seems to be rebooting fine.  Thank you for your help!