DHCP Client Won't Start

[PackerIntl]

This is a new one on me, and very puzzling. If anyone has any ideas, PLEASE
chime in.

I have a client with a Windows XP Pro, SP3 notebook. A couple of weeks ago,
they could no longer connect it to their DHCP server. In trying to find the
problem, I did find that it had a root kit, AV killer, which I think I got
rid of. However, when I start the system, the DHCP client service will not
start. It is set to Automatic. As near as I can tell, the dependency
services/drivers are going. It just won't start on it's own. If I go to the
services console, I can start it manually.

I have tried the published procedures for repairing the Winsock and the
TCP/IP stack. No help.

The problem exists for both the wired and the wireless connections. I have
tried uninstalling both of those and letting them reinstall; still no help.

 

[John Wunderlich]

This is a new one on me, and very puzzling. If anyone has any
ideas, PLEASE chime in.

I have a client with a Windows XP Pro, SP3 notebook. A couple of
weeks ago, they could no longer connect it to their DHCP server.
In trying to find the problem, I did find that it had a root kit,
AV killer, which I think I got rid of. However, when I start the
system, the DHCP client service will not start. It is set to
Automatic. As near as I can tell, the dependency services/drivers
are going. It just won't start on it's own. If I go to the
services console, I can start it manually.

I have tried the published procedures for repairing the Winsock
and the TCP/IP stack. No help.

The problem exists for both the wired and the wireless
connections. I have tried uninstalling both of those and letting
them reinstall; still no help.

There was a post virtually identical to yours in the Microsoft
Forums.

<http://social.answers.microsoft.com...k/thread/cc08d289-4ede-4fca-bd7c-bf63daf6b8ad>

The poster was able to solve his problem using the
procedure at the following URL:

<http://www.geekstogo.com/forum/Rootkit-help-atapi-sys-t270282.html&p=1776132#entry1776132>

HTH,
John

 

[pcs365.10]

Hi PackerIntl,

DHCP Client Service may not start automatically. When you attempt to start the Service manually, the following error may be displayed:

Error: Could not start the DHCP Client Service on local computer
Error 1068: The dependency service or group failed to start.

Resolution
The DHCP Client Service in Windows XP, depends on these three components:
* AFD
* NetBios over Tcpip
* TCP/IP Protocol Driver

If one of the above drivers fail to start, then the DHCP Client Service may not start.
Step I - Make sure that the three driver files are present

Open Windows Explorer and navigate to /Windir/System32Drivers folder. Make sure that the following files are present in the folder:

* afd.sys
* tcpip.sys
* netbt.sys

If one or more of the above driver files are missing, extract them from the Windows XP CD-ROM or from the ServicePackFilesi386 folder, whichever is the latest version.

Step II - Verify the number of Dependencies

From other sources in the Web, I've found that some versions of Norton Antivirus (NAV) adds an entry to the DHCP Service Dependencies, and removing NAV does not remove the appropriate value from the DHCP Dependencies.

To quickly determine the Dependency services for DHCP Client Service, type the following command in Start, Run dialog:

CMD /K SC QC DHCP

Verify the output. It should be exactly as below:

[SC] GetServiceConfig SUCCESS

SERVICE_NAME: dhcp
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:WINDOWSsystem32svchost.exe -k netsvcs
LOAD_ORDER_GROUP : TDI
TAG : 0
DISPLAY_NAME : DHCP Client
DEPENDENCIES : Tcpip
: Afd
: NetBT
SERVICE_START_NAME : LocalSystem

If additional entries are listed under DEPENDENCIES…
If any other additional drivers or Services are mentioned in the DEPENDENCIES section, you need to remove them via the registry. Follow these steps:

* Click Start, Run and type Regedit.exe
* Navigate to the following branch:
* Backup the branch to a REG file

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Dhcp

* Double-click DependOnService MULTI_SZ value and set it's data as follows:

Tcpip
Afd
NetBT

* Close Regedit.exe

Step III - Verify that the Dependency Service / components are running

Next step is to verify that the three dependency components are running. As the three components are actually the Kernel Drivers (Driver Service), you need to manage then via the Device Manager. Follow these steps:

* Click Start, Run and type DEVMGMT.MSC
* In the View menu, click Show hidden devices
* Double-click Non-Plug and Play drivers section
* Double-click the entry - AFD Networking Support Environment, and click the Driver tab
* Set the Startup type to System.
* Start the service. Note down the error message if any.
* Similarly start the two other drivers namely:

* TCP/IP Protocol Driver
* NetBios over Tcpip

* Close Device Manager and restart Windows.

Regards,
Chris

Please reply at your convenience.