21 Posts

March 12th, 2006 00:00

Try to follow this instruction:

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%\System32\Drivers 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 ServicePackFiles\i386 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:\WINDOWS\system32\svchost.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, 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.

3 Posts

March 13th, 2006 12:00

thanks for the input - I will try to get it operational this evening- I wasted most of sat. trying to figure out what was wrong -

3 Posts

March 18th, 2006 16:00

I ran through the check list - the drivers seem to be there and operating - during the step 2 check there were a couple of things not exactly the same as was listed -  one was at the start_type: it reads :1 system_start instead of the :2 auto_start -- is this something that needs to be changed? The other item that was different was on the bottom line it says : localsystem but it does not show a [/code] reference after the word system - are these issues?    I am way over my head with this issue - can I reload or restore something? thanks.
No Events found!

Top