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
-
1
- #21
I cam across this very same issue twice in the last week (1st time I had to re-install complete new WinXP), but I think I got it now. I was able to re-establish the connection to the Internet. 
I had all the issues describes above (IP=0.0.0.0, "netsh" failed, etc). I have combined some partial Win2K methods(there you can uninstall TCP/IP), which then changed my problem to the famous 169.254.x.x problem (where DHCP cannot be connected), then I re-installed XP - and it works!
These are the steps I've used (mybe not everything is necessary:
01. Use Regedit.exe to navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock.
02. Export the Winsock key to a Winsock.reg file, to save it.
03. Delete the Winsock key.
04. Navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2.
05. Export the Winsock2 key to a Winsock2.reg file, to save it.
06. Delete the Winsock2 key.
07. Exit Regedit.exe.
08. Execute in a Command window: "netsh int ip reset c:\resetlog.txt". This time it ends successfully, the IP is now "169.254.x.x" (which is another problem).
09. Re-install WinXP with the installation CD (use the "upgrade" option).
After the re-installation completed, I got everything back.
Let us know does it work to you too.
BTW: I had this problem twice after using Ad-Aware 6.0 (the spyware cleaner) which deleted some files and registries off my computer. I am still using it and "usually" there is no harm.
I had all the issues describes above (IP=0.0.0.0, "netsh" failed, etc). I have combined some partial Win2K methods(there you can uninstall TCP/IP), which then changed my problem to the famous 169.254.x.x problem (where DHCP cannot be connected), then I re-installed XP - and it works!
These are the steps I've used (mybe not everything is necessary:
01. Use Regedit.exe to navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock.
02. Export the Winsock key to a Winsock.reg file, to save it.
03. Delete the Winsock key.
04. Navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2.
05. Export the Winsock2 key to a Winsock2.reg file, to save it.
06. Delete the Winsock2 key.
07. Exit Regedit.exe.
08. Execute in a Command window: "netsh int ip reset c:\resetlog.txt". This time it ends successfully, the IP is now "169.254.x.x" (which is another problem).
09. Re-install WinXP with the installation CD (use the "upgrade" option).
After the re-installation completed, I got everything back.
Let us know does it work to you too.
BTW: I had this problem twice after using Ad-Aware 6.0 (the spyware cleaner) which deleted some files and registries off my computer. I am still using it and "usually" there is no harm.
I've encountered the same problem twice. Once on a Windows XP home and once on a Windows XP Professional machine.
The first time, I tried a lot of "things" and eventually did a full reinstallation.
Today I've read OISA's solution, tried it out and HOERAY HOERAY, it works!!! My customer will be happy to get his machine back, with all his soft preserved.
Thanks a lot OISA!
Greetings
The first time, I tried a lot of "things" and eventually did a full reinstallation.
Today I've read OISA's solution, tried it out and HOERAY HOERAY, it works!!! My customer will be happy to get his machine back, with all his soft preserved.
Thanks a lot OISA!
Greetings
ok, I ran adaware 6 and it accidentally deleted some registry keys and I have the same exact problem. I did that regedit thing to export the winsock and winsock 2. I also tried to reinstall winxp but only the components. After I did that something went terribly wrong. Whenever my compute starts the explorer bar freezes and svchost.exe is about 100% processor usage. I'm basically locked out of my computer and I can't do anything. Can someone please help me?
I had excactly the same problem after using Ad-Aware 6.0, but the method that OISA presented us with works great!!!
So tnx OISA
I also have a comment on the post from dauss. My cpu load also went to 100% and explorer also frose. Nevertheless, you can press CTRL-ALT-DEL and fire up your taskmanager in order to kill svchost.exe. But be warned!! only pick the one with the highest cpu load, else you might get a message saying that windows is going to shutdown in a few moments. After that you should have a 'normal' cpu load, and might even be able to use explorer normally. You can than follow the steps of OISA in order to repair windows.
My advise on this is: just use cmd, thats all you need
So tnx OISA
I also have a comment on the post from dauss. My cpu load also went to 100% and explorer also frose. Nevertheless, you can press CTRL-ALT-DEL and fire up your taskmanager in order to kill svchost.exe. But be warned!! only pick the one with the highest cpu load, else you might get a message saying that windows is going to shutdown in a few moments. After that you should have a 'normal' cpu load, and might even be able to use explorer normally. You can than follow the steps of OISA in order to repair windows.
My advise on this is: just use cmd, thats all you need
-
14
- #25
A less drastic measure than reinstalling XP is to use this utility, What this set of files does is in essence the approach recommended here, but does not require reinstalling XP or losing all of your updates.
The utility first deletes the keys winsock and winsock2 from the registry. It then replaces the registry entries with winsock and winsock2 from a fresh XP install. Finally, it does a netsh int ip reset resetlog.
It works great, and yes AdAware is what forced me to find some alternative other than reinstalling XP.
The utility first deletes the keys winsock and winsock2 from the registry. It then replaces the registry entries with winsock and winsock2 from a fresh XP install. Finally, it does a netsh int ip reset resetlog.
It works great, and yes AdAware is what forced me to find some alternative other than reinstalling XP.
My link above was corrupted by the word What. The link is:
chaser1972
Technical User
Grrrr Adaware! there was me being all IT department like and chastising the user for having so many spyware items that needed deleting, when as soon as i delete them, the poor bloke goes and loses all network connectivity! managed to find this thread (thanks to all!) and have the tool at the bottom provided by bcastner. now it automatically gives me an ip address of 169.xx etc and am unable to release or renew this. if i try putting in a static address it accepts it but won't let me get anywhere. the event viewer comes up with a few errors along the lines of "support for the specified sockket type doesn't exist in this address family" any ideas anyone> thanks in advance
Try the newer version of the Fix, it more comprehensively goes through the catalogue of adapters:
Should do the trick.
Should do the trick.
chaser1972
Technical User
wonderful! thank you very much indeed. adaware was my favourite tool in the whole world until today. i wonder if lavasoft know of their over zealous apps flaws?
Hi all,
I follow all microsoft steps, found a IPMONTR.DLL messages error, then found this site, great!
I applied winsockFix.zip, voila, it work fine.
Maybe not adware6 problem at all, I was in trouble after install and check Imesh 4. Adware restore was effective, then I did partials clears. The problem was when, lately, I uninstalled Imesh 4.
Have fun !
I follow all microsoft steps, found a IPMONTR.DLL messages error, then found this site, great!
I applied winsockFix.zip, voila, it work fine.
Maybe not adware6 problem at all, I was in trouble after install and check Imesh 4. Adware restore was effective, then I did partials clears. The problem was when, lately, I uninstalled Imesh 4.
Have fun !
Riki2002,
There are countless reasons for corrupted Winsock stack errors: new adapters, removal of old adapters, adapter driver updates, registry cleaners, anti-virus tools, spybot cleaners, malware cleaners, etc. If you have one or some of these:
. The adapter is not in a state permissable for this operation
. 0.0.0.0 as the IP address, DNS address, Gateway address
. ipconfig /renew error messages
. netsh int ip reset reset.log does not change anything
. There is not enough memory to complete the operation on any ipconfig or Network Connection status check
and many more possible errors, a rebuild of your Winsock stacks has a good chance of repairing the problem. I am glad the utility linked above worked for you.
I mention in the interest of completeness one obscure source of DHCP errors: removal of Norton Anti-Virus using just the Add/Remove program option. I wasted two days on this one. A good site discussing the problem and a workaround for this:
There are countless reasons for corrupted Winsock stack errors: new adapters, removal of old adapters, adapter driver updates, registry cleaners, anti-virus tools, spybot cleaners, malware cleaners, etc. If you have one or some of these:
. The adapter is not in a state permissable for this operation
. 0.0.0.0 as the IP address, DNS address, Gateway address
. ipconfig /renew error messages
. netsh int ip reset reset.log does not change anything
. There is not enough memory to complete the operation on any ipconfig or Network Connection status check
and many more possible errors, a rebuild of your Winsock stacks has a good chance of repairing the problem. I am glad the utility linked above worked for you.
I mention in the interest of completeness one obscure source of DHCP errors: removal of Norton Anti-Virus using just the Add/Remove program option. I wasted two days on this one. A good site discussing the problem and a workaround for this:
RayCampbell
Technical User
Greetings from Atlanta! Be sure that you are using Build 0162, not 0160, of Ad-aware 6.0. On the Ad-aware 6 Status screen, click the Information button (i) to the far right of the Ad-aware 6.0 logo to view the build number.
I've used winsockfix to fix corruptions in tcp/ip on my windows xp system but now my mcafee firewall will not work. I have un-installed the firewall and re-installed it. This allows the firewall to startup but tcp/ip is corrupt again. I have to use winsockfix again to get my internet connectivity working. Does anyone have any ideas?
If you see this try the following
open a command window, e.g. start - run - type "CMD" - enter
Type FTP some known ip address
Look for socket errors, if found you must edit registry for winsock errors.
Alternately ty performing system restor, we are seeing this happen when P2P file sharing progarms installed...e.g. kazaa, etc.
Try cleaning the spyware out with a utility like adaware.
latest version is 6 from download.com
There is also a utility called lsp-fix from cexx web site dedicated to spyware removal......
good luck. call center help desk guy
open a command window, e.g. start - run - type "CMD" - enter
Type FTP some known ip address
Look for socket errors, if found you must edit registry for winsock errors.
Alternately ty performing system restor, we are seeing this happen when P2P file sharing progarms installed...e.g. kazaa, etc.
Try cleaning the spyware out with a utility like adaware.
latest version is 6 from download.com
There is also a utility called lsp-fix from cexx web site dedicated to spyware removal......
good luck. call center help desk guy
![[thumbsup2]](/data/assets/smilies/thumbsup2.gif "[thumbsup2] [thumbsup2]")
It sounds silly, but I attempted to enurmerate all the possible TCP/IP errors one could experience from a corrupted Winsock service stack.
This particular thread gets picked up by a Google, Group search, and I wanted to make it as extensive as possible. If you had a Winsock error that was fixed, no matter the version of Windows, I would appreciate it if you posted here so as others can see the thread with a Search from Google or other search engine.
And, I am happy it worked for you.
Best.
Bill Castner
This particular thread gets picked up by a Google, Group search, and I wanted to make it as extensive as possible. If you had a Winsock error that was fixed, no matter the version of Windows, I would appreciate it if you posted here so as others can see the thread with a Search from Google or other search engine.
And, I am happy it worked for you.
Best.
Bill Castner
I did run the Winsock Fix, (thanks BCastner), but still could not start the DHCP service. I found another post regarding Norton leaving a service in the registry after being uninstalled:
I had to remove the value "SYMTDI" from the end of
HKLM\System\CurrentControlSet\Services\DHCPDependOnService
Check out MSKB article 812335 for more info.
So, basically it was two different problems!
I am now up and running! Hope this post might benefit someone else!
I had to remove the value "SYMTDI" from the end of
HKLM\System\CurrentControlSet\Services\DHCPDependOnService
Check out MSKB article 812335 for more info.
So, basically it was two different problems!
I am now up and running! Hope this post might benefit someone else!
Not only was Internet Explorer failing for me, I was unable to install Microsoft ActiveSync, which I use to connect my Pocket PC to my laptop. When I tried installing ActiveSync, I would get the following error:
The TCP/IP Protocol must be installed on this computer before Microsoft ActiveSync can be installed.
Click OK to quit Setup. Then, open Control Panel, double-click Network, and install this protocol.
Well, I did have TCP/IP installed (it is, after all a core component for Windows XP).
After running WinsockFix, ActiveSync installed without a problem.
The TCP/IP Protocol must be installed on this computer before Microsoft ActiveSync can be installed.
Click OK to quit Setup. Then, open Control Panel, double-click Network, and install this protocol.
Well, I did have TCP/IP installed (it is, after all a core component for Windows XP).
After running WinsockFix, ActiveSync installed without a problem.
dstone1234
IS-IT--Management
Another save for the WinsockFix.
After playing around with the "Create New Connection" tool of the "Network Connections" control, I deleted a network bridge. After that, no internet connectivity.
Every other machine on my network continued to draw a DHCP address (so my DHCP server was working), but the machine on which I was working drew the APIPA address of 169.254.xxx.xxx. It wouldn't renew ("ipconfig /renew", giving an error that indicated a problem with the socket. When I manually configured the machine's IP to an address in the network's subnet, I had successful pings on loopback, local machines, machines across the router, and to internet machines by IP (but not by name) (so the hardware was working). Eventually, I found the XP network diagnostic tool that showed "DHCPSERVER=255.255.255.255(InvalidIP)," putting me on the right path. I restarted the DHCP Client on the machine (and all the clients upon which it depends), but it didn't solve the problem. Searching Google for "DHCPSERVER=255.255.255.255" indirectly led me here.
I did encounter the problem with McAfee FW (going to tackle that now), but wanted to say thanks for the bigger problem solved.
After playing around with the "Create New Connection" tool of the "Network Connections" control, I deleted a network bridge. After that, no internet connectivity.
Every other machine on my network continued to draw a DHCP address (so my DHCP server was working), but the machine on which I was working drew the APIPA address of 169.254.xxx.xxx. It wouldn't renew ("ipconfig /renew"
, giving an error that indicated a problem with the socket. When I manually configured the machine's IP to an address in the network's subnet, I had successful pings on loopback, local machines, machines across the router, and to internet machines by IP (but not by name) (so the hardware was working). Eventually, I found the XP network diagnostic tool that showed "DHCPSERVER=255.255.255.255(InvalidIP)," putting me on the right path. I restarted the DHCP Client on the machine (and all the clients upon which it depends), but it didn't solve the problem. Searching Google for "DHCPSERVER=255.255.255.255" indirectly led me here.I did encounter the problem with McAfee FW (going to tackle that now), but wanted to say thanks for the bigger problem solved.
- Status
Similar threads
- Locked
- Question