Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
LinkBack | Thread Tools | Display Modes |
|
|||
DHCP Client service does not start because of dependency failure
My user's Dell M1330 laptop recently bought is not able to get connected to
networks both with the NIC and the Wireless card. We know the router is not the problem because other Desktop (wired connection) and Laptop (wireless) can connect to the router just fine. The problem is basically because the laptop NIC is not getting an IP address assigned by DHCP server, and further investigating revealed that the DHCP Client service is not started (although it was set to automatically start). We couldn't manually start the service and got an 1608 error saying dependency group failed (without telling us which one failed). Looking in the dependency tab of the DHCP Client shows these are components the service depends on: Ancillary Function Driver for Winsock NetIO Legacy TDI Support Driver TCP/IP Protocal Driver Network Store Interface Service NSI proxy service We checked and know the NSI proxy service is running fine. We can ping 127.0.01 and I think that means the TCP/IP Protocal Driver is working fine. So that leaves the AFD driver in question. So how can we find out if the AFD driver has been loaded correctly? Thanks for any help or pointer! Best, Lanny |
|
|||
DHCP Client service does not start because of dependency failure
I finally figured it out.
To test is AFD is loaded correctly, first start CMD as an administrator, and then type net start AFD As I suspected, the AFD driver couldn't be loaded. And I had to use sfc /scannow to repair the corrupted driver file. Once it's repaired, I started DHCP Client service just fine and I was able to get DHCP assigned IPs with no problem. Hope this will help someone else who experience the same problem. Best, Lanny "Lanny Lin" wrote: My user's Dell M1330 laptop recently bought is not able to get connected to networks both with the NIC and the Wireless card. We know the router is not the problem because other Desktop (wired connection) and Laptop (wireless) can connect to the router just fine. The problem is basically because the laptop NIC is not getting an IP address assigned by DHCP server, and further investigating revealed that the DHCP Client service is not started (although it was set to automatically start). We couldn't manually start the service and got an 1608 error saying dependency group failed (without telling us which one failed). Looking in the dependency tab of the DHCP Client shows these are components the service depends on: Ancillary Function Driver for Winsock NetIO Legacy TDI Support Driver TCP/IP Protocal Driver Network Store Interface Service NSI proxy service We checked and know the NSI proxy service is running fine. We can ping 127.0.01 and I think that means the TCP/IP Protocal Driver is working fine. So that leaves the AFD driver in question. So how can we find out if the AFD driver has been loaded correctly? Thanks for any help or pointer! Best, Lanny |
|
|||
DHCP Client service does not start because of dependency failure
Hi, I'm having this problem- and when I tried what you said - it came back with 'Acess is denied'' How can I have access denied?! -- dack8472 |
|
|||
DHCP Client service does not start because of dependency failu
You have to run CMD as an administrator.
To do that, you type in CMD after you click the START button. Then right click on Command Prompt from the list and select Run as Administrator. "dack8472" wrote: Hi, I'm having this problem- and when I tried what you said - it came back with 'Acess is denied'' How can I have access denied?! -- dack8472 |
|
|||
DHCP Client service does not start because of dependency failure
I did the same fix and the sfc scan came back that no errors were detected... Now what can I do???? -- digga19 |
|
|||
DHCP Client service does not start because of dependency failure
Lanny mate, take a bow!
Had this issue end of last year, there is NOTHING anywhere else to fix it. Since i first fixed it, you have literally saved me rebuilding 4 machines that my colleagues are like 'herp derp' and i just refer them to Mr. Lanny Lin! Thank you a million times! I work level 1 helpdesk. Your fix is now my favourite knowledge base article!! On Friday, November 2, 2007 3:28:01 PM UTC+11, Lanny Lin wrote: My user's Dell M1330 laptop recently bought is not able to get connected to networks both with the NIC and the Wireless card. We know the router is not the problem because other Desktop (wired connection) and Laptop (wireless) can connect to the router just fine. The problem is basically because the laptop NIC is not getting an IP address assigned by DHCP server, and further investigating revealed that the DHCP Client service is not started (although it was set to automatically start). We couldn't manually start the service and got an 1608 error saying dependency group failed (without telling us which one failed). Looking in the dependency tab of the DHCP Client shows these are components the service depends on: Ancillary Function Driver for Winsock NetIO Legacy TDI Support Driver TCP/IP Protocal Driver Network Store Interface Service NSI proxy service We checked and know the NSI proxy service is running fine. We can ping 127.0.01 and I think that means the TCP/IP Protocal Driver is working fine. So that leaves the AFD driver in question. So how can we find out if the AFD driver has been loaded correctly? Thanks for any help or pointer! Best, Lanny |