Replace corrupt TCP/IP stack

[mucous]

We had a problem about a year ago where access to terminal services and OWA began behaving very badly (no one could access OWA and terminal service ran extremely slow). After many attempts to resolve the problem, we thought the TCP/IP stack had gotten corrupted so I tried to rebuild it, but didn't do it right and it caused some bad problems. Eventually, it was done and all was well again.

It looks like we're having this same problem again and I was hoping to get some advice on rebuilding the stack so I don't kill our servers this time around.
We have a Win2k file server with terminal services and an exchange 2000 server for our mail and OWA. Last time this happened I took out TCP/IP on the file server in an attempt to replace the stack not realizing it would cause problems. The office was knocked out for around 3 hours while I frantically tried to reinstall it. Finally got it done and the terminal services and OWA began working again, but this somehow messed up Active directory on the Exchange server and I had to uninstall, then reinstall that also.

I sure would appreciate anyone's advice on how to properly rebuild the TCP/IP stack without killing everything!

By the way...our VPN is SonicWall on the Pro230 box if that helps.

Again, thanks to anyone with some advice...

 

[mucous]

Doh! I should have mentioned that our VPN was very slow also. This was what originally brought the trouble to our attention, then we found Terminal services and OWA had problems too.

 

[markdmac]

http://support.microsoft.com/?id=299451

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[mucous]

Mark,

Thanks. The post is definitely helpful. I created more trouble for myself last time I tried rebuilding the TCP/IP stack because I didn't have this info. Hopefully your help will make it less painful this time around. I'm not looking forward to this at all.

Thanks again and have a good day!