DHCP Client not starting

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

sim2k_supportAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mcsweenSr. Network AdministratorCommented:
There should be an error logged in Event Viewer when you try to start this service.  Can you please paste that error in here?
0
sim2k_supportAuthor Commented:
The DHCP Client service terminated unexpectedly.  It has done this 1 time
Event ID 7034
Source: Service Control manager.
0
Bill_FleuryCommented:
Have you ran through the troubleshooting steps listed here:

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

0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

zeddianCommented:
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.
0
sim2k_supportAuthor 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.
0
zeddianCommented:
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!).  

0
mcsweenSr. Network AdministratorCommented:
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
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mcsweenSr. Network AdministratorCommented:
Which one did it, the winsock fix or system file checker?
0
valleycomputerworksCommented:
nets winsock reset worked for me
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.