Dhcp client issues

[drs1771]

I had a laptop come in today that won't obtain an IP address from a dhcp router. I found the dhcp client service wouldn't start. It was giving me a 1608 error due to one of the dependabilites failing to start. I repaired the driver that was failing and now all three dependencies start on boot, but dhcp will not. I have to go in and manually start it even though it is set to start automatically in the services.msc. I also checked to see if it was enabled under services in msconfig, and it is. I've been on it all day, and am at a loss. The service will start everytime I tell it to restart, but it won't start automatically on boot. Any ideas fellow sharks?

[ua549]

Have you configured it to restart after a failure?
What is the error code now that the dependency issues are resolved?
What are the related entries, if any, in the system event log?

[drs1771]

I have all three fail options set to restart at 1 minute intervals. There isn't an error code being generated now and the service will start, but not automatically.

I didn't even think to check the event log. I have a service or driver that fails to start called 'tdx'. I'm not sure what this driver is, but it is a network driver or service of some sort.

I tried the sfc command, and it gets about 26% done, then says some files are corrupt and can't be repaired.

This tdx service is not listed in the dependencies, should it be?

Thanks for the look, ua!

[drs1771]

OK, the log tells me the DHCP client service was terminated because there are no more enpoints available from the endpoint mapper. The event ID is 7023. I'm lost here...

[ua549]

I suggest 3 things:

1. Resolve the issues with the sfc errors. You may need to do a repair install.

2. The tdx.sys issue is usually due to a partially non-compliant with the OS NIC driver. It can cause the DHCP error. Get the latest NIC drivers.

3. If the DHCP error recurs, open a CMD window and enter SC query dhcp and note the exit codes.