installed Win 2K3 Server and created Terminal Server. THis server is connected to a Win 2K Domain Controller. The problem I am having is my NIC erros out or disconnects after a certian amount of time (10mins - 30mins.) I have changed NICs out, updated drivers tried different PCI slots. Has anyone seen a problem with Win 2K3 losing NIC cards in Device Manager? Please e-mail me.

I would check hardware settings such as switch/hub and NIC. Robert Lin, MS-MVP and MCSE For more tips and information go to http;//www.chicagotech.net

I have checked all switches and I have two other servers running on them and the are fine. But I double checked all hardware. I cann't find anything with the hardware right off. If I go to device manager there is either a yellow ! or a red X on the nic card. I have tried an Intel Pro 100 managment adaptor and a Netgear FA311 with updated drivers from both the parent websites. I have tried different PCI slots. Nothing works. I get the connection for about 10 - 30 mins and then it goes away. I have to reboot the server for the connection to come back. Please anyone help, I am trying to get a Terminal Server up for remote sales team. Even if you just have some good troubleshooting forums, Tech sites etc...

Any info in event viewer? Sure a lot but you will have to comb every bit. I would disconnect the new server from all lan's and see if the NIC's go green. If they are ok without any connection then look to things like dns or domain controller or wins being out of whack. Dup IP's dup names? If the hardware shows red or yellow then you will need to find out why at the server. The lan cables should not be connected while doing an install of the card. (my opinion) Also do you have any lan test equipment? I think that the intel does offer some testing ability. Before I would be pulling any hardware out be sure to uninstall it from the hardware manager. It might be that an old version of the device driver is causing it.

I figured out the problem if anyone needs to know go to this knowledge base artical and read. Some of the actual symptoms may very but if you are having a similar issue this should fix it. http://support.microsoft.com/default.aspx?scid=kb;en-us;821467 Q821467 I called them and they did not charge me they said ok and sent me the patch, very quick and easy, no questions asked.

Thanks for the update. From what you report and what MS reports I wouldn't have thought it to be the same problem.