While working on another problem, I had a remote co-worker uninstall tcp/ip protocol from their local area connection under a windows 2000 professional computer and they rebooted and I want them to add it back in by doing the same thing and going in and install then protocol but they do not have that option? I know that I have done this before so not sure why they can't. Is there a way to do this without original cd? Thanks, Joe
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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can't reinstall tcp/ip protocol.
- Thread starter jjjax
- Start date
- Thread starter
- #3
Control Panel, Folder Options, View, Show hidden files and folders.
The following is XP-centric, but the notion is the same:
The following is XP-centric, but the notion is the same:
suggests you should install another protocol while TCP/IP uninstalled.
Also XP centric, but the linked WinsockFix utility works perfectly fine for Win2k: faq779-4625
The utility linked includes a seperate registry section depending on whether it runs under win9x, NT, Win2k or XP. It is very safe to use.
The utility linked includes a seperate registry section depending on whether it runs under win9x, NT, Win2k or XP. It is very safe to use.
Wolluf,
For Win9x, ME and Win2k, no.
For XP, yes -- to the extent that a Netsh int ip reset resetlog.txt does
For all of the above it:
. it disables all network adapters, and attempts to remove "Ghost" adapter entries if they exist.
. it deletes the registry entries for Winsock and Winsock 2, and replaces them with a registry merge of a "virgin" installation -- OS dependent.
. it re-enables the adapters
. In the case of XP, it runs "netsh int ip reset resetlog.txt"
. it tries to make sure the HOSTS file is clean.
And then appropriately asks for a reboot.
I hope that helps.
For Win9x, ME and Win2k, no.
For XP, yes -- to the extent that a Netsh int ip reset resetlog.txt does
For all of the above it:
. it disables all network adapters, and attempts to remove "Ghost" adapter entries if they exist.
. it deletes the registry entries for Winsock and Winsock 2, and replaces them with a registry merge of a "virgin" installation -- OS dependent.
. it re-enables the adapters
. In the case of XP, it runs "netsh int ip reset resetlog.txt"
. it tries to make sure the HOSTS file is clean.
And then appropriately asks for a reboot.
I hope that helps.
- Thread starter
- #9
- Thread starter
- #10
Looks good!
She is in another location without another internet connection so I could not have her download any utilities so I had her delete the winsock and winsock2 entries in the registry as described in the MS article then added the tcp/ip protocol by using have disk option and going to with winnt\inf folder because it still wasn't showing on the original list to select. It made her reboot and everything was fine after that. Thanks for the help!
She is in another location without another internet connection so I could not have her download any utilities so I had her delete the winsock and winsock2 entries in the registry as described in the MS article then added the tcp/ip protocol by using have disk option and going to with winnt\inf folder because it still wasn't showing on the original list to select. It made her reboot and everything was fine after that. Thanks for the help!
- Status
Similar threads
