Sign in with
Sign up | Sign in
Your question

DHCP Client Service Won't Start - Error 1068

Last response: in Networking
Share
July 20, 2009 9:13:24 PM

Edit:
I've been researching the problem as much as I can. So my DHCP Client Service Won't Start, I get Error 1068 Which is the dependency services or group failed to start. The dependencies I have for the DHCP Client Service are Ancilliary Function Driver for Winsock, NetIO Legacy TDI Driver (Hit + Sign to get TCP/IP Protocol Driver), Network Store Interface Service (+ sign to NSI proxy service). The only service from that list I see under Services is the Network Store Interface Service and it is started.

Now I don't know where to go from here. I read that Norton could mess with this service, I had Norton 360 but switched to AVG about 6 months ago and have had no problems in the meantime.


Original Post:
Starting yesterday I haven't been able to connect to my network via Ethernet.

I'm using the onboard network adapter from my ASUS M2N32-SLI Deluxe mobo and Vista Ultimate 64 Bit. Under device manager my network adapter is NVIDIA nforce 10/100/1000 Mbps Ethernet. That's a generic name, I checked my mobo specs and it's specifically a NVIDIA nForce 590 SLI MCP. I have the latest driver which is 67.8.9.0. My router is a Linksys WRT54GSv4.

I want to use a dynamic IP address, I have a static IP set up on my wireless and that's working fine right now. But I can't connect using either of my Ethernet ports. I've switched ports on my router, but my 360 connects no problem so I don't think it's the router.

Under network connections my Local Area Connection is stuck on "Identifying..." If I double click it and click details I have no default gateway. Belarc Advisor tells me DHCP Server: none responded.

That's as much information that I can think of, but I can't figure out why I can't connect.
July 21, 2009 7:33:52 PM

Under services I can see that Network Store Interface Service is running. I followed those steps and when I typed net start AFD on cmd I was told that the service is already running. So that leaves TCP/IP, but I am able to ping 127.0.01 so I don't know what the problem could be here.
Related resources
July 22, 2009 1:41:23 AM

Go to your router's config page and change the DHCP on your router to "dynamic".

On your computer's adapter, try fixing your tcp/ip--http://support.microsoft.com/kb/811259. It maybe corrupt.
Go to local area property and under tcp/ipv4, make sure you "obtain ip automatically".

Go to your cmd window and type ipconfig /all and let me know what you get.
July 22, 2009 5:10:25 AM



Only DHCP setting I see on any of my router's pages, this is the basic setup page.

I checked out that link:

Quote:
Manual steps to determine whether the Winsock2 key is corrupted for Windows Vista users

1. Click Start, click Run, type Msinfo32, and then click OK.
2. Expand Components, expand Network, and then click Protocol.
3. Ten sections appear under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
* MSAFD Tcpip [TCP/IP]
* MSAFD Tcpip [UDP/IP]
* MSAFD Tcpip [TCP/IPv6]
* MSAFD Tcpip [UDP/IPv6]
* RSVP UDP Service Provider
* RSVP TCP Service Provider
* RSVP UDPv6 Service Provider
* RSVP TCPv6 Service Provider
* MSAFD NetBIOS [\Device\NetBT_Tcpip...
* MSAFD NetBIOS [\Device\NetBT_Tcpip...
* MSAFD NetBIOS [\Device\NetBT_Tcpip...
* MSAFD NetBIOS [\Device\NetBT_Tcpip...
* MSAFD NetBIOS [\Device\NetBT_Tcpip...
* MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on such as proxy software installed.
...
If there are fewer than ten sections, there is information missing.


I have these 8 sections:

* MSAFD Tcpip [TCP/IP]
* MSAFD Tcpip [UDP/IP]
* MSAFD Tcpip [TCP/IPv6]
* MSAFD Tcpip [UDP/IPv6]
* RSVP UDP Service Provider
* RSVP TCP Service Provider
* RSVP UDPv6 Service Provider
* RSVP TCPv6 Service Provider

So I'm missing 2x MSAFD NetBIOS [\Device\NetBT_Tcpip... entries.

Diagnose and Repair doesn't help, none of the options are able to fix my problem. I reset Winsock using the steps provided and still I have only 8 sections.

I have "obtain ip automatically" selected.


ipconfig /all results:


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Tyler-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8187 Wireless 802.11b/g 54Mbps
USB 2.0 Network Adapter
Physical Address. . . . . . . . . : 00-15-AF-0D-C2-AF
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b941:f4f6:8d0d:6c4f%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.87.78.130
68.87.85.98
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
Physical Address. . . . . . . . . : 00-1B-FC-53-2C-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1B-FC-53-24-6A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::943b:5324:1c3b:1f5f%8(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.31.95(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 68.87.69.150
68.87.85.102
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{7305B48F-3515-4CA2-B0EC-5C0CB7773
1A1}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{552F3C14-2014-4A0E-90CD-7E4536311
984}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.hsd1.wa.comcast.net.
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Windows\system32>

July 22, 2009 2:56:05 PM

This is on the same computer? First of all, it looks like you have TWO adapters--one wireless (usb) and the other Ethernet. You can have both, but turn off the wireless for now and work with your Ethernet only.

If you look at your DHCP setup, the ipaddress assigned to your computers should be between 192.168.1.100 to 192.168.1.255. Your current ip on your Ethernet adapter is 169.x.x.x which means the DHCP is not able to assign the number it wants.

1. Check the cables
2. Restart the router
3. Disable the wireless adapter on the computer
4. Restart the computer. On your local area connection, make sure the adapter is not disabled.
5. Do another ipconfig /all. You should see only the ipaddress for the Ethernet between the two numbers mentioned above. If the DHCP can't assign those numbers, you won't get anything (internet, file sharing, etc).

If you don't get the right number:
6. bring up the cmd window. Type ping 192.168.1.1 If you can't ping it, wiggle the cable, check your driver, etc. if you can't ping it, you can't do anything else. If you can ping it, proceed to
7. On the cmd window, type ipconfig /renew. Then type ipconfig /all to see if you have the right numbers.
8. Tell me what happens.



Tyler1986 said:
Edit:
I've been researching the problem as much as I can. So my DHCP Client Service Won't Start, I get Error 1068 Which is the dependency services or group failed to start. The dependencies I have for the DHCP Client Service are Ancilliary Function Driver for Winsock, NetIO Legacy TDI Driver (Hit + Sign to get TCP/IP Protocol Driver), Network Store Interface Service (+ sign to NSI proxy service). The only service from that list I see under Services is the Network Store Interface Service and it is started.

Now I don't know where to go from here. I read that Norton could mess with this service, I had Norton 360 but switched to AVG about 6 months ago and have had no problems in the meantime.


Original Post:
Starting yesterday I haven't been able to connect to my network via Ethernet.

I'm using the onboard network adapter from my ASUS M2N32-SLI Deluxe mobo and Vista Ultimate 64 Bit. Under device manager my network adapter is NVIDIA nforce 10/100/1000 Mbps Ethernet. That's a generic name, I checked my mobo specs and it's specifically a NVIDIA nForce 590 SLI MCP. I have the latest driver which is 67.8.9.0. My router is a Linksys WRT54GSv4.

I want to use a dynamic IP address, I have a static IP set up on my wireless and that's working fine right now. But I can't connect using either of my Ethernet ports. I've switched ports on my router, but my 360 connects no problem so I don't think it's the router.

Under network connections my Local Area Connection is stuck on "Identifying..." If I double click it and click details I have no default gateway. Belarc Advisor tells me DHCP Server: none responded.

That's as much information that I can think of, but I can't figure out why I can't connect.

July 23, 2009 4:06:00 AM

Cables: check, router: check.

Here is the ipconfig /all with my Wireless Connection disabled (the wireless is on board as well).


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Tyler-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
Physical Address. . . . . . . . . : 00-1B-FC-53-2C-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1B-FC-53-24-6A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::943b:5324:1c3b:1f5f%8(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.31.95(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 68.87.69.150
68.87.85.102
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{7305B48F-3515-4CA2-B0EC-5C0CB7773
1A1}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{552F3C14-2014-4A0E-90CD-7E4536311
984}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.hsd1.wa.comcast.net.
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Windows\system32>




Still the wrong number. So I tried to ping like you said:


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 169.254.31.95: Destination host unreachable.
Reply from 169.254.31.95: Destination host unreachable.
Reply from 169.254.31.95: Destination host unreachable.
Reply from 169.254.31.95: Destination host unreachable.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Windows\system32>


Did the ipconfig /renew and no luck because of the message: An error occurred while renewing interface Local Area Connection : The RPC server is unavailable.



Edit:

So I'm come across some more stuff. None of these three services will start:

DNS Client
IP Helper
DHCP Service

All with error 1068 Dependency service failed to start. So it must be something with my TCP/IP Protocol Driver since all three share the dependency service of NetIO Legacy TDI Support Driver > TCP/IP Driver and it is the only dependency of DNS Client.
July 23, 2009 7:39:55 PM

Also you might want to go to safe mode and see if you can't get the services started there.
July 23, 2009 10:39:17 PM

Checked it out and that fix isn't applicable. Thanks though. And I tried Safe Mode and DHCP can't be started from safe mode, I'll have to try Safe Mode with Networking.

One thing I noticed. If I went into regedit and then to hklm\system\currentcontrolset\services\dhcp. Click DHCP, then in the right pane, Dependency Services, I modified the file and removed tdx which there are three entries : AFD, TDX, NSI. Now I can start DHCP and access the internet.

But not everything is fixed. Accessing the internet wasn't really my problem, I can use my wireless connection no problem. Since my problems I've lost the ability to share files with my xbox 360 which is really annoying since I watch a ton of stuff that way.

So DNS Client and IP Helper still won't start. So it gave my internet but still hasn't solved my problems. It still appears to me that my TCP/IP driver might be broken (for lack of a better word) seeings how I had to remove it from the dependency list to get DHCP to start and the 2 other services that depend on it still will not start.
July 23, 2009 11:33:24 PM

Can you do ipconfig /all again. You have internet access now? That means you computer is at least talking to the router.
July 23, 2009 11:44:14 PM

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Tyler>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Tyler-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
Physical Address. . . . . . . . . : 00-1B-FC-53-2C-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1B-FC-53-24-6A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::943b:5324:1c3b:1f5f%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, July 23, 2009 3:21:34 PM
Lease Expires . . . . . . . . . . : Friday, July 24, 2009 3:21:34 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 201333756
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-4B-51-5E-00-1B-FC-53-24-6A

DNS Servers . . . . . . . . . . . : 68.87.69.150
68.87.85.102
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{7305B48F-3515-4CA2-B0EC-5C0CB7773
1A1}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{552F3C14-2014-4A0E-90CD-7E4536311
984}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.hsd1.wa.comcast.net.
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Tyler>
July 24, 2009 12:00:57 AM

DNS Servers . . . . . . . . . . . : 68.87.69.150 68.87.85.102 ?

DNS Server should point to the router. It does on mine. On yours, it should be 192.168.1.1 Check to make sure your IP4v properties is set on "dns server automatically" and ipconfig /all to see it changes.
July 24, 2009 12:41:08 AM

While I'm no networking whiz, I'm pretty sure the DNS Servers are correct. I thought DNS servers had something to do with your ISP. I use those same DNS server addresses on my Static IP settings for my wireless (on my desktop) and they are the same numbers viewed on my laptops dynamic IP settings for it's wireless. Not sure if it matters, either, but my DNS Client is not running and won't start because of the same error.
July 24, 2009 1:09:19 AM

If you open up your Router's Config page, the wan side is assigned by your ISP. Those are probably the 68.x.x.x numbers. But your dhcp will auto assign your ipaddress, gateway, dhcp and dns. Your dns should be on auto.

If your dns needs to resolve an ipaddress, it will direct it to the router and your router to the internet.
July 24, 2009 1:25:38 AM

Under my IPv4 settings for LAN it is set to auto, but it isn't for my static IP (desktop wireless) Also, those same DNS addresses are given on my laptop which is set to be acquired automatically.

I'm not trying to argue the DNS point here, I don't really know. I do know, however, that I have had these DNS addresses long before my problems with my services not starting began to show up. These numbers have never given me problems and have always been there.

Do you think this problem stems from something possibly wrong with my TCP/IP Driver as it pertains to the 2 other services I still cannot start, seeings how if I were to edit that service back into my DHCP Service's dependency services it would not start either.
July 24, 2009 1:51:46 AM

Try this:

Reset TCP/IP stack to installation defaults by typing on the cmd window: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog
July 24, 2009 7:15:31 AM

I've tried the winsock command before, and the netsh int ip reset is all I typed, adding the reset.log gave me an error.

Unfortunately, no go. The other two services still won't start.
July 24, 2009 2:43:25 PM

Originally you had 2 adapters, one wireless and the other cabled. Is it possible you were using one to connect to the internet and the other to share files? What's the intended goals again? Did you want to share files that is on this computer or files in your xbox 360?

Do you have a backup image of your system partition?
July 24, 2009 7:16:02 PM

I still have two adapters. My wireless is set up with a static IP address, it's just set up because I have it. Before this problem arose I didn't need it. I could access the internet through my wired connection which used a dynamic IP address. I share files from my PC to my 360 using my wired connection. I can't successfully stream my video over my wireless connection. Plug in an cat V and bam, works. Now I've been having problems and my wired connection stopped working.

As of now I can start my DHCP service and get internet over my wired connection by removing TDX (the tcp/ip driver) from the dependency services list for DHCP. DNS Client and IP Helper will still not start, which have tdx as a dependency service. Which makes me think there is a problem with the TCP/IP driver, but I've used the command to reset them to default and it still doesn't work.

No backup image.
July 26, 2009 1:27:56 AM

I don't know what else to recommend. But if you ever do reinstall the os and you get it working, i would definitely make a backup image. use acronis or norton ghost to make it. if you ever have any problem with the system, just reimage and it takes about 20 minutes or less.

Before you install your os, make sure you create at least two partitions. One for the system and one for your docs. Good Luck!
July 26, 2009 7:18:31 PM

Yeah I was just thinking I may have to reinstall, well, that is, wait until I get a copy of windows 7 and just upgrade.
July 26, 2009 9:55:44 PM

Preordered my upgrade a couple of weeks ago for $50. Unfortunately, I have to wait 'till it comes out in late October.

Backing up your system image is the most efficient way to get you going asap. I keep 2 or 3 images of the system. One with just the OS, OS+drivers and OS+drivers and programs. It's a lot more reliable than restore points which I never use anymore. If there is something wrong with the system, be it from virus, trojan, messed up driver...I just reimage. If I want to mess with a program I've downloaded from the internet for free and it messes my system...reimage. There is not one problem it cannot solve...unless your hard drive goes caput. Anyway, good luck.
Anonymous
July 7, 2010 4:26:53 PM

RPC Server error usually means the DHCP Client, DNS Client, RPC Server is not started in the Services.msc. I found DHCP is the only one that would not start so here is my Fix.

DHCP Client Service Won't Start - Error 1068

Device Manager – Show hidden Devices and AFD will be list bad/not working
Uninstall AFD and go to CMD and enter sfc /scannow
I used a reinstall Dell CD for the XP Pro I needed and that worked to reload the AFD driver.
It repairs the AFD driver and then go to your services and Start DCHP Client.
My Internet then worked for me.

Hope this helps

Firestouch

Thanks to

http://www.vistax64..ilure.html
January 19, 2012 4:49:02 AM

I am going to share few tricks with you that have helped various users. You too perform these tricks in order to solve the said error:

1. Start Dependent Services for Windows Firewall
2. Start Dependent Services for the Print Spooler Service
3. Fix Registry and Clear Web Browser Cache
4. Start Dependent Services for Internet Connection Sharing

The Error 1068 in Windows 7 may still occur if your registry is not properly configured.
If you have already been experiencing the error 1068 error. You can also get some help from this article error 1068.

Hope it fix your problem.
January 21, 2012 4:57:25 PM

Everything posted here and about 10 other sites did not fix this symptom for my case.
Symptoms included:
"Limited or no connectivity" message for the local area connection (it was "no" in fact)
"DHCP Client" got the 1068 dependency error when I Started it in service.msc.
AFD service not shown in Services.msc, yet afd.sys was present in Device Manager in the non-plug-and-play drivers (hidden) area, which said it was started.
The same was true of netbios.sys.
netbt.sys was in neither place.
All services with dependency on AFD or DHCP were not started, and gave the error when one tried to Start them.
The registry showed that the NetBT key had no values. The sub-keys were there (enum, etc) but not the Start, Type, ImagePath, or other values in the key
HKLM/SYSTEM/CurrentControlSet/NetBT
The event viewer showed recent abnormal terminations for java.exe.
Configuration of the router and of the TCPIP advanced properties both looked normal.
ipconfig showed address 0.0.0.0, and ipconfig -renew failed


WDO Beta (Win Defender Offline) succeeded in booting and in updating over the internet, so all hardware problems were 99.9% ruled out.

After a reboot into XP and then a reboot back into WDO, the only detection was the recent Java/CVE-2011-3544.e . Some sites suggest that it messes up one or more of the networking drivers. In my case the point was netbt.sys, but perhaps it could vary. After cleaning of Java/CVE, and rebooting, there was nothing detected by WDO . But the symptoms all remained the same.

More things which Failed to fix it:
uninstall and reinstall of networking protocols, clients, etc
disable and re-enable of NIC & network connections
removal of various game-software components, including Pando
removal of all toolbars and most browser extensions
removal of a "cracked" Vegas-9 program (the PC is owned by an inexperienced person)
delete of "Hamachi" connection
Intel ProSet (to test the Broadcomm onboard network hardware.)
Update of drivers from Dell as suggested by Dell.com (it is a Dell GX-280).
netsh reset command
sfd -scannow command
restore (the PC had no good restore points)
Boot into "Safe mode with networking" and install service packs and windows updates.

My hunch was that the lack of netbt.sys was the problem, even though it is not a listed dependency of AFD.sys . So:

!!!!!!!!!!
DO NOT ATTEMPT THE BELOW UNLESS YOU ARE EXPERIENCED WITH "REGEDIT" , AND KNOWLEDGEABLE IN GENERAL. YOU COULD DO MORE HARM THAN GOOD.
!!!!!!!!!

How I fixed it:

1. Exported the HKLM/SYSTEM/CurrentControlSet/ registry entries from a working machine and brought those on a thumb drive.
2. Backed up the registry in the bad PC. Using notepad to read the export, and regedit to make changes, I created equivalent values in the /NetBT key. For "ImagePath", i used the same folders as other drivers, not the value from the other machine. If it is unclear to you, SEE ABOVE WARNING. Note that similar infections might damage keys such as afd, tcpip, netbios, ipsec, and/or netbt .
3. Rebooted. At this point, the "limited or no connectivity" went away for the first time.
4. Updated and ran a series of antimalware programs : MalwareBytes, Spybot S&D, WDO Beta, avast. The first two detected plenty more and reported that they successfully fixed them all. avast had been running all along while the infection occurred (sorry avast, just the facts!), so it makes sense that it found no problems again.
5. Updated Java to patch the vulnerability itself.
6. rebooted for the 37th time.
7. Tightened security settings a lot.
8. Lectured user.

Things seem OK now. HTH
!