lnqtechservices
asked on
DHCP server service stuck on 'starting'
We have recently rebuilt our domain controller base with Windows 2003. Occasionally our centres lose power and when the server reboots it gets stuck starting the DHCP server service. No error is returned because the service hasn't actually failed, it's still 'starting' according to the Services app. As a result, clients don't receive an IP address, techs can't remote into the server (we are not on-site). The server responds to ping and we can use mmc snap-ins to access services and so on, but the server is not fully 'up'. We did not have this problem with Windows 2000 Server, in the same physical environment. Please help!
ASKER
It doesn't always occur when power is dropped either. I have restarted several servers remotely and they have still come up with the dhcp server service saying 'starting'. And it never finishes starting. Sometimes we can rdp into the server check the services but mostly not, when this is occurring. At the moment all we can do is pull power repeatedly until the server comes up properly. Not our preferred method! Is anyone listening?
did you check the DHCP log under c:\windows \system32\dhcp ????
ASKER
Yes it seems only to deal with leases as far as I can read it. There are no entries that might suggest why the service does not start properly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
toniur that would be a great idea.
ASKER
Toni's solution showed promise. We could make the dhcp service dependent on something like Microsoft Firewall (installed with ISA 2004) or another service that starts later in the boot sequence, to ensure any services that dhcp depends on have loaded. We have actually moved the dhcp function off the server onto the router. There haven't been further problems at this stage.
Thanks!
Thanks!
ASKER