View Full Version : Fix A Mangled IP Configuration XP
RanGer498
19th October 2002, 01:36 AM
In the days before Windows XP, a corrupted IP installation could often be fixed simply by removing and reinstalling TCP/IP. In most cases, the IP-related files remained intact, but some related Registry keys would be corrupted beyond repair.
You can't uninstall TCP/IP in Windows XP, because there is no Uninstall button for this protocol. According to Microsoft, that is because TCP/IP is an integral part of the operating system, and removing it would cause major problems. You can, however, use the Windows XP command line utility NetShell to reset all IP-related Registry settings to their default values. The result is a brand-new TCP/IP configuration.
The Netsh.exe program is located in the C:\Windows\ System32 directory. To use the program, enter the command "netsh int ip reset filename." You must specify a filename, such as Ipstuff.txt. After Netsh .exe runs, the file will contain a detailed log of the Registry keys that were modified.
^7_of_9
19th October 2002, 05:30 AM
OMG .... What a coincidence that you posted this today. I myself just used this exact same command today to clear out a problem I had with connecting to my ISP. If I can remember correctly the command I used was: netsh interface ip reset restlog.txt
It's nasty to have to go through the command line for all of this now but it works. After running the command you need to reboot the machine and then will possibly have to release and renew the IP address a few times then reboot again after doing that and it should work.
So the Sequence is:
Run the Command.
Reboot
Release IP
Renew IP
Release IP
Renew IP
Release IP
Renew IP
Reboot.
Surf the Interet or or browse your network.
If you tell me it's a big PITA doing it this way instead of the old way!
TGC
19th October 2002, 05:43 AM
Don't know about WinXP, but in earlier versions of WinNT and Win2K is it not easier to just use the ipconfig command @ a command prompt to change the settings?
speculative
19th October 2002, 08:38 AM
Thanks for the tips guys; was looking to tweak my network settings - this college LAN I'm on is utter carp if you ask me. I'm seriously thinking about getting DSL next semester instead, seeing as how this LAN is slower than dial-up a great deal of the time. :(
-spec
dodgygeeeza
19th October 2002, 11:32 AM
nice one ranger,iv'e been going mad and my brain is nearly back to normal after 2 days of trying to fix my browser to get back on the forums for some answers,as you say fixing this problem with win98 was easy, but not so with xp,the only way i was able fix it was to install netscape and this seemed to fix the problem, thanks for the heads up on the correct way to fix it...;)
^7_of_9
19th October 2002, 04:03 PM
Originally posted by TGC
Don't know about WinXP, but in earlier versions of WinNT and Win2K is it not easier to just use the ipconfig command @ a command prompt to change the settings?
In WinXP it won't let you renew the IP address properly if it's DHCP through ipconfig.
TGC
20th October 2002, 01:49 AM
even if you specify the adapter? Strange, makes one think that maybe this would not be a good Network OS, or they do not believe the end-users are smart enough to know anything about networking. :rolleyes: :confused:
^7_of_9
20th October 2002, 02:01 AM
Yeah even though I did a ipconfig /renew Rogers (I named the adapter Rogers after the ISP) and it always came out as a DHCP timeout. Once I used the above sequence I posted everything was ok.
TGC
20th October 2002, 03:23 AM
Sounds like a bug in the code to me, question is weither it is actually an accidental bug or by design? :)
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.