Hi, I've been running Internet Explorer on my Windows XP for months. It's not working any more. I narrowed down the problem to when i do IPCONFIG /RENEW, i get msg error occurred while renewing interface local area connection 3 : the system can not find the file specified. My network connection configured to obtain an IP address automatically an an IP address 0.0.0.0, I was trying to start the DHCP client service (right click My computer, then Manage, Services and Apllications, Services, then DHCP client) the service status remains STARTING, but never gets started ! I don'T know how to repair the registry for this DHCP client service ? Also, when i do NETSH INT IP RESET, i get Initilization function INTHELPERDLL in IPMONTR.DLL failed to start with error code 1010. I need help !!!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to start DHCP client service after renew lease failed 20
- Thread starter Pingc
- Start date
Sorry, xp pro, the other one being xp home. I'm assuming this problem is more with the invasive nature of the ad software than the removal software, presumably it trys to cause a pc to cling on to the same ip address or something.
Thanks in anticipation! I've found SO many articles/threads on this that have ended up with reinstalls, which seems unreasonably extreme!
Thanks in anticipation! I've found SO many articles/threads on this that have ended up with reinstalls, which seems unreasonably extreme!
DHCP errors can be rough.
1. I assume you did WinsockFix faq608-4650
2. If you ever uninstalled Norton Antivirus, see: 3. If there are more than one DHCP servers, you can obtain your result. For example, your DSL modem is really a modem/router. You connect a broadband router. Result: DHCP failure. Resolve this my changing your broadband router to a different local IP network segment base address. For example, setting the broadband router to 10.0.0.1 and using 10.0.0.x for your LAN will work.
4. Firewall software can do this.
5. Antivirus software with "hidden" firewall components can do this. e.g. PC-Illan.
1. I assume you did WinsockFix faq608-4650
2. If you ever uninstalled Norton Antivirus, see: 3. If there are more than one DHCP servers, you can obtain your result. For example, your DSL modem is really a modem/router. You connect a broadband router. Result: DHCP failure. Resolve this my changing your broadband router to a different local IP network segment base address. For example, setting the broadband router to 10.0.0.1 and using 10.0.0.x for your LAN will work.
4. Firewall software can do this.
5. Antivirus software with "hidden" firewall components can do this. e.g. PC-Illan.
I've run all the winsock fix and the other utilities mentioned, tcp/ip is working, because I can get net access with a manually configured ip. I have a cable modem running through a netgear router, which is heavily used (many different pcs connected from time to time) with no problems, the problem only ocurred immediately after running ad aware. I felt quite snug behind the nat of the router until I started reading up, hence running ad aware! I haven't uninstalled norton, I use zone alarm, although the problem exists whether it's enabled or not. Other pcs are still getting ip automatically, just tried a repair on an unaffected pc and it's ok.
What is the 'afd' entry in dependant services? should it be there?
What is the 'afd' entry in dependant services? should it be there?
Netbios helper service should start if 'enable Netbios over TCP/IP' is checked in the box under TCP/IP Properties, Advanced, WINS tab.
A failure of DHCP client service to start explains your issue. Is the Workstation, and the Server services started?
The usual recommendation, and a good one, is to reinstall Windows as a repair or "in-place" upgrade.
A slightly off-the-official recommendation to do try for Windows XP only:
1. Do steps #2 - #3 in my FAQ faq608-4650
2. Follow "AlexJ" 's second comment here:
A failure of DHCP client service to start explains your issue. Is the Workstation, and the Server services started?
The usual recommendation, and a good one, is to reinstall Windows as a repair or "in-place" upgrade.
A slightly off-the-official recommendation to do try for Windows XP only:
1. Do steps #2 - #3 in my FAQ faq608-4650
2. Follow "AlexJ" 's second comment here:
Pheeeww!
While eagerly awaiting you reply, I did a google on afd networking ..blah and found the location of it, in non plug and play devices, in device manager, also looked at netbios over tcp/ip and found it's startup type to be 'disabled'. Lo and behold, dhcp starts!
So
1: What disabled it in the first place?
2: Why couldn't services manager start it?
3: why don't we look in the easy place first?
MANY thanks for your help, maybe this will help someone else one day!
While eagerly awaiting you reply, I did a google on afd networking ..blah and found the location of it, in non plug and play devices, in device manager, also looked at netbios over tcp/ip and found it's startup type to be 'disabled'. Lo and behold, dhcp starts!
So
1: What disabled it in the first place?
2: Why couldn't services manager start it?
3: why don't we look in the easy place first?
MANY thanks for your help, maybe this will help someone else one day!
Many services require that another service has started succesfully.
Control Panel, Administrative Tools, Services, if you look at any individual service it will show its dependencies.
This is not always a completely accurate list. It lists only dependent services. You need to use Win2k or XP resource tools such as "depends.exe" to really trace the issue.
In your case XP by default does not enable the setting under TCP/IP properties, Advanced, WINS to "enable Netbios over TCP/IP". To the Windows designers, this is a compatability mode setting and should not be needed for stricly XP-to-XP networking.
Glad you got it sorted.
To review:
Check that your Computer Browser, DNS service, DHCP service, Workstation, Server, and Netbios Helper service are all running. You can adjust these later, in some cases, but check their status first. They should be running when trying to diagnose DHCP problems.
Control Panel, Administrative Tools, Services, if you look at any individual service it will show its dependencies.
This is not always a completely accurate list. It lists only dependent services. You need to use Win2k or XP resource tools such as "depends.exe" to really trace the issue.
In your case XP by default does not enable the setting under TCP/IP properties, Advanced, WINS to "enable Netbios over TCP/IP". To the Windows designers, this is a compatability mode setting and should not be needed for stricly XP-to-XP networking.
Glad you got it sorted.
To review:
Check that your Computer Browser, DNS service, DHCP service, Workstation, Server, and Netbios Helper service are all running. You can adjust these later, in some cases, but check their status first. They should be running when trying to diagnose DHCP problems.
BrainDeadGone
Technical User
Since this thread led to my resolving the same problem, I thought I'd post my experience as well.
The problem I ran into was the one described above -- IP=169.254.x.x, "netsh" seemed to run successfully but did not resolve the problem, manually deleted the Winsock registry entries and updated TCP/IP over itself, etc. Jumping right to the bottom line, the solution to the problem was to delete the Network Bridge from the Network Connections and reboot.
Background: I experienced this problem on two different home PCs (from Gateway & Dell) both running Windows XP Home.
The problem manifested itself the same way both times, even though the problems occurred about a year apart. I had been using each PC successfully for months, turned on the PC one day, and lost network connectivity. I had not installed any software or made any system changes during my previous session on the PC. The first PC was cabled into a LinkSys DSL/Cable broadband router which was plugged into a cable modem from my ISP. The second PC was plugged into a newer LinkSys DSL/Cable Wireless broadband router which was also plugged into a cable modem from my ISP. In the second scenario, another PC in my house had a concurrent wireless connection to the router but did not experience the problem.
After unsuccessfully trying all the suggestions listed above (except deleting the Network Bridge) with my first PC, I resolved the problem by reinstalling WinXP. With the second PC, I also unsuccessfully tried all the suggestions above before deleting the Network Bridge. I found that I could resolve the problem each time I rebooted the PC by Repairing the Network Bridge. Of course, I wanted a permanent solution and so I tried deleting the Network Bridge and then rebooting. This solution was permanent and I'm posting this reply from that PC.
Hopefully this experience will help someone else with the same issue.
The problem I ran into was the one described above -- IP=169.254.x.x, "netsh" seemed to run successfully but did not resolve the problem, manually deleted the Winsock registry entries and updated TCP/IP over itself, etc. Jumping right to the bottom line, the solution to the problem was to delete the Network Bridge from the Network Connections and reboot.
Background: I experienced this problem on two different home PCs (from Gateway & Dell) both running Windows XP Home.
The problem manifested itself the same way both times, even though the problems occurred about a year apart. I had been using each PC successfully for months, turned on the PC one day, and lost network connectivity. I had not installed any software or made any system changes during my previous session on the PC. The first PC was cabled into a LinkSys DSL/Cable broadband router which was plugged into a cable modem from my ISP. The second PC was plugged into a newer LinkSys DSL/Cable Wireless broadband router which was also plugged into a cable modem from my ISP. In the second scenario, another PC in my house had a concurrent wireless connection to the router but did not experience the problem.
After unsuccessfully trying all the suggestions listed above (except deleting the Network Bridge) with my first PC, I resolved the problem by reinstalling WinXP. With the second PC, I also unsuccessfully tried all the suggestions above before deleting the Network Bridge. I found that I could resolve the problem each time I rebooted the PC by Repairing the Network Bridge. Of course, I wanted a permanent solution and so I tried deleting the Network Bridge and then rebooting. This solution was permanent and I'm posting this reply from that PC.
Hopefully this experience will help someone else with the same issue.
Brain dead gone... your isp was proly blocking bridged coonections(opens back door into network). The reason that is have founs to be the cause of most of the exact symptoms described is removal of a firewall with the firewall enabled. As the best that i can determine, the filter stays in winsock by way of a registry key that enables the firewall. when the registry key is removed sometimes the winsock dll must be replaced in order to reset the binary value somewhere in the dll. Bcastners fix has help me numerous times in fixing the problem, but most times when i run into errors such as these is simply delete and extract the winsock and wsock32 ddl's using msconfig, ensureing that thw winsock protection is disabled.....which leads to the other possible root of the problem...the uninstallers may not remove or alter the reg key for winsock protection when removing the firewall and this would explain the need for the winsock reinstall as well.
the only right answer to "why?" is: "why not?"
the only right answer to "why?" is: "why not?"
I concluded eventually, (after re running ad aware and having no problem) that it was not the culprit, it was one of grc's security utilities, the most likely being the DCOMbobulator which turned off the service, it's one of those things where you think 'I'll know that for next time', but each time it comes up it's a different cause! the next time, with a customer's m/c it was my doom that had done some bad things (tech speak I know!) giving that same symptoms, I think it had been trying to redirect traffic via another DNS, and removing it left no connectivity. In that case winsock fix sorted it right away.
I had a very similar problem in that the DHCP service would not start, nor would the netlogon service. Adaware was not installed on the system, and neither was Norton Antivirus. The user simply stated that the battery on a laptop had died and the system went down. When the system was restarted that's when the fun began.
This is a Windows 2000 system. Removing TCP/IP and reinstalling did not help. Reg cleaners and service pack updates also didn't help. After finding this thread I tried the WinsockFix and the problem was solved.
Thanks to all
This is a Windows 2000 system. Removing TCP/IP and reinstalling did not help. Reg cleaners and service pack updates also didn't help. After finding this thread I tried the WinsockFix and the problem was solved.
Thanks to all
I'm thinking I might have the same issue. I have two PC's hooked up to my network (cable modem/linksys hub). Both PC's show a transfer speed of 100MPS. I'm using Charter Communications diagnostic tool and it says it cannot find the network connection even though the connections are enabled. I cannot release using ipconfig/all, ipconfig/release. It cannot find these files. Does this sound like the same issue?
One thing I haven't seen mentioned is the startup dependancies. If you navigate to the registry> HKey local machine/system/currentcontrolset/services/NetBT, doubleclick on the start value, be sure it is set to 1 and hexidecimal. Mine was changed to 4 by Norton's which prevented NetBT from starting which in turn prevented dHCP from starting due to its dependancy on NetBT.
maxnix
maxnix
Check this out. Fixing a PC with bad HD. Bought new 80GB Deskstar to replace crappy old 8.5GB Maxtor.
Got it in.
Fresh install of XP.
Installed Ad Aware version 6.
Did all the critical updates for XP.
Internet connection and DHCP dies.
I was already weeping and gnashing my teeth because of wireless networking woes (suffice to say I think it's all a crock of crap...at least with a Linksys WRT54G it is), so I switch to regular LAN....and then this. I looked in services for a clue, and found that DHCP Client hadnt started. When I tried to start it, it told me one of the dependencies failed to start. If you look at those dependencies, they arent just other services, they are things like TCP/IP Protocol driver. And it doesnt seem to elude to which one has failed. And how do you check that anyway? Anyway, thanx to this fantastic forum here, I found the answer in the Winsock fix file. After running it and rebooting, XP automatically did a chkdsk, and found that nwlnkft.dll was corrupted. According to some other sources online, this is some sort of IPX packet traffic filter or something like that. The chkdsk seemed to take care of it.
I read above that someone said the newer versions of Ad Aware supposedly fixed this kind of behavior. I'm pretty sure this is the newest version. I checked the forums on Lavasofts site dealing with this issue, and suggestions from the moderators are things like "completely uninstall old versions prior to installing new ones" and "keep the default search options," etc. None of that applies to my situation.
I have had to go through the same complete install process a number of times during the past month or so. I generally install all the same stuff (it's generally all stuff I have installed on my own machines) and never had this problem before.
I wont rule out the possibility that Netgear's Wireless Configuration Utility had nothing to do with it. This is part of the install for the wireless adapter I tried to use at first. Aside from all the usual wireless problems I always have, I had a new one - the utility would constantly start and stop, to where my system tray was constantly resizing to accomodate it. I did uninstall the software and the driver before proceeding with any of the windows updates or anything.
The point is I champion that winsockfix file as the quickest, easiest solution. And I consider wireless networking a nice bedtime story for children (at least if you have a WRT54G, like me).
Got it in.
Fresh install of XP.
Installed Ad Aware version 6.
Did all the critical updates for XP.
Internet connection and DHCP dies.
I was already weeping and gnashing my teeth because of wireless networking woes (suffice to say I think it's all a crock of crap...at least with a Linksys WRT54G it is), so I switch to regular LAN....and then this. I looked in services for a clue, and found that DHCP Client hadnt started. When I tried to start it, it told me one of the dependencies failed to start. If you look at those dependencies, they arent just other services, they are things like TCP/IP Protocol driver. And it doesnt seem to elude to which one has failed. And how do you check that anyway? Anyway, thanx to this fantastic forum here, I found the answer in the Winsock fix file. After running it and rebooting, XP automatically did a chkdsk, and found that nwlnkft.dll was corrupted. According to some other sources online, this is some sort of IPX packet traffic filter or something like that. The chkdsk seemed to take care of it.
I read above that someone said the newer versions of Ad Aware supposedly fixed this kind of behavior. I'm pretty sure this is the newest version. I checked the forums on Lavasofts site dealing with this issue, and suggestions from the moderators are things like "completely uninstall old versions prior to installing new ones" and "keep the default search options," etc. None of that applies to my situation.
I have had to go through the same complete install process a number of times during the past month or so. I generally install all the same stuff (it's generally all stuff I have installed on my own machines) and never had this problem before.
I wont rule out the possibility that Netgear's Wireless Configuration Utility had nothing to do with it. This is part of the install for the wireless adapter I tried to use at first. Aside from all the usual wireless problems I always have, I had a new one - the utility would constantly start and stop, to where my system tray was constantly resizing to accomodate it. I did uninstall the software and the driver before proceeding with any of the windows updates or anything.
The point is I champion that winsockfix file as the quickest, easiest solution. And I consider wireless networking a nice bedtime story for children (at least if you have a WRT54G, like me).
Try updating the firmware in your linksys, a friend has a linksys and brand new out of the box wouldn't work consistently, until the firmware was upgraded. I've got various adaptors and having played around and had all the probs you've had and maybe some more besides I just don't have them any more, I put it down to now knowing what the terms mean, i.e. what to put in what box, I find that I can hook a new card up to the network in seconds. I use netgear routers, and had nightmares with the first one (took DAYS to get it working at all!), but now find it goes ok setting up a new one, just a learning curve, I think. One thing I have found though is be sure to uninstall any previous adaptor software before installing a new one, it just won't see a new one if the old stuff is there. I'm pretty sure that adaware doesn't cause problems with services, it's the malicious stuff that adaware removes that's the problem, by it's nature you don't notice it arrive, could be from the first site you visit, One of the m/c s I've had this sort of problem with went back, and all ok, a few weeks later, they wanted to know their ip address, so I thought easy way, get them to log into my web server and i'd just let them know the ip from the log, each visit triggered visits from theirs, and about 5 other ips moments later, I can assume that they've got yet another 'menace' that's tracking their activity.
- Status
Similar threads
- Locked
- Question