Quote: "Hi. From what I have learned about DHCP is it is only needed when you are connected to the internet and need an IP address. It is for dynamic IP addresses and if you are using static IP address, there is again not much use for DHCP. WHen it is set to automatic, that means it isn't going to run until it is called for. I COULD be mistaken, but this is my take on the subject." That is not exactly correct... DHCP Client attached to a network allows your networked machine connect to a service and get an IP address. If your client cannot connect to a DHCP server you will not be able to connect to anything unless your network all share the MS dafault IP range of 169.x.x.x. <b>Quick Google Search</b> <b>Symptom</b> DHCP Client Service may not 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 installation of Norton Antivirus (NAV) adds an entry to the DHCP Service dependencies, and removing NAV does not remove the corresponding entry from the DHCP Dependencies. To view the dependency services registered 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 value and set its 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. Follow the steps below: 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

Quote: "Hi. From what I have learned about DHCP is it is only needed when you are connected to the internet and need an IP address. It is for dynamic IP addresses and if you are using static IP address, there is again not much use for DHCP. WHen it is set to automatic, that means it isn't going to run until it is called for. I COULD be mistaken, but this is my take on the subject." That is not exactly correct... DHCP Client attached to a network allows your networked machine connect to a service and get an IP address. If your client cannot connect to a DHCP server you will not be able to connect to anything unless your network all share the MS dafault IP range of 169.x.x.x. <b>Quick Google Search</b> <b>Symptom</b> DHCP Client Service may not 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 installation of Norton Antivirus (NAV) adds an entry to the DHCP Service dependencies, and removing NAV does not remove the corresponding entry from the DHCP Dependencies. To view the dependency services registered 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 value and set its 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. Follow the steps below: 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