Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
We have been having problems with a Win 2000 network regarding TCP/IP. (We run Win 2000 server, SP2).
For no apparent reason, we lost the ability to use the Internet, closely followed by the ability to use any type of network connection. Immediately afterwards the server began to constantly crash with the all to familiar Blue screen claiming an error in "tcpip.sys". In short, we cannot even ping a computer on the network anymore!
We are attempting to re-install Tcp/ip, but cannot work out how to do this directly, and without reinstalling windows 2000 server completely. Win 2000 does not appear to let you uninstall TCP/IP from LAN --> properties --> TCP/IP.
Will reinstalling a win 2000 service Pack reinstall TCP/IP? Are there any diagnostic tools we can use to check the status of the tcp/ip configuration of win 2000? Or should we just "give up", and reset our server completely?

You might have some luck running win2k's System File Checker (SFC.exe) from the command prompt. I don't remember the exact command but you can get them with a /? switch. This should check all the files for changes from the original install media and replace them if necessary. I believe this also effectively removes the service pack.

Thanks for the suggestion ..... however ....
When trying to run sfc.exe we are asked for our win 2000 server installation CD. We insert it, but are told that it is the incorrect CD. This is definately not the case .... it is certainly the correct CD. It is however, and upgrade CD .... surely Windows is not expecting our old NT4 Cd?? We do not have this any longer!!
There is no apparent way to force sfc to use the CD ... we cannot "browse" for the CD.Any ideas?

I had similar problems with Windows 2000 Professional. One day it decided not to access the web anymore, but it could ping, do a trace route even by DNS names locally, or over the web. There were no BSODs on my machine and no error messages in the event viewer. I went through the same steps as you did. Removed/changed the NIC same/different PCI slot, updated the driver, applied/re-applied the SP, etc. I've even done the "sfc /scannow" with no difference. Ended up re-installing W2K and that fixed it. Evidently the problem wasn't hardware related after all.

I know there is a way to reinstall TCP/IP without reinstalling Windows, but I forget how. I think Glen posted an answer on the forum once. Try doing a search and see what turns up, or maybe Glen (if it was him) will add his input again....

Right click my network places/properties then right click local area connection/properties click on tcp/ip and uninstall.say yes to the warning reboot when prompted and it will reinstall if it doesent use same method and install protocol tcp/ip.

AS I stated in my original mail, this does NOT work, as we are running Windows 2000 server. It would appear you cannot individually remove TCP/IP from 2000 server, probably because it is assuming that any server would require it. You can only uninstall TCP/IP in this way using win 2000 clients .... or at least this is true on our system!
Dave.

Sorry it took awhile for me to reply. I was on a short vacation. As you found out, you can not uninstall TCP/IP on W2k Server because TCP/IP is required for Active Directory. You may want to try to remove and reinstall Client Services for Microsoft. I have done this in the past with similar errors. After a reboot, your system will seem to hang for awhile at "Preparing Network Connections" because it can not find things but it will come up eventually, maybe up to 5 mins or so. Then reinstall Client for Microsoft Networks and see what happens. You could reinstall too I suppose but I'd try this first.
Good luck.

Many thanks for your help.
In the end we decided to re-install SP2, and see if this re-copied, and / or somehow reset the problem files.
This appears to have worked, as the Server is at least stable at the moment.Dave.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |