DHCP Client not starting

sim2k_support
sim2k_support used Ask the Experts™
on
Windows XP Pro laptop can not connect to a network using DHCP, wireless or hard wired.  The DHCP Client does not start Automatically even though it is listed to do so.  If you attempt to start it manually through services you get the following error

Could not start the DHCP client service on Local Computer.  
Error 1067: The process terminated unexpectedly.

I also get no error in Event Viewer.  I can connect to a network assigning a Static IP Address.  I have tried editing the DependOn Value in the Registry Key with no success.  Any help would be greatly appreciated.

Thanks
SIM2K

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Bradley FoxLAN/WAN Systems Administrator

Commented:
There should be an error logged in Event Viewer when you try to start this service.  Can you please paste that error in here?

Author

Commented:
The DHCP Client service terminated unexpectedly.  It has done this 1 time
Event ID 7034
Source: Service Control manager.
Have you ran through the troubleshooting steps listed here:

http://windowsxp.mvps.org/dhcp.htm

CompTIA Network+

Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.

Commented:
It sounds like a dependency issue.  Enter this at a command prompt: CMD /K SC QC DHCP
This will list the service dependencies.  Some anti-virus programs will insert themselves a dependencies for dhcp, if that service fails then dhcp will not start.  Look at the dependencies of the services from services.msc and see if any of the normal services (afd.sys, tcpip.sys, netbt.sys) have failed to start.  If there are any other depnedencies, they aren't standard and may be the cause of the issue.

Author

Commented:
Both solutions posted are essentially the same thing and neither worked.  I have only the standard dependencies and the 3 are started.  Any other suggestions would be greatly appreciated.

Commented:
Outside of virii and malware, you may just have a corrupt system file.  The common element here is tcp so you may want to reset tcp/ip (netsh int ip reset c:\resetlog.txt).  Also running the system file checker may solve the problem (with disks on hand!).  

LAN/WAN Systems Administrator
Commented:
Try running these at a command prompt restarting after each to see if DHCP will start.  Make sure you have your XP CD handy for the second.

netsh winsock reset
sfc /scannow
Bradley FoxLAN/WAN Systems Administrator

Commented:
Which one did it, the winsock fix or system file checker?
nets winsock reset worked for me

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial