- Dec 21, 2000
- 5,280
- 0
- 71
Hey fellas! I'm setting up a trial version of Windows 2003 Server to kind of dink-around with. It's on a dual P3 866MHz system with 1GB of SDRAM. I currently have a Netgear FA311 NIC in there. Here's the problem:
Sometimes, but not always - 3 out of 5 boots - the NIC doesn't start up with Windows. Win2K3 says that there is 'limited or no connectivity' through the adapter and I have to mess with the settings to get the NIC to work. (ie: disable/enable the NIC, renew IP, restart the system, etc etc) Since I'm trying to base the use of this machine over Remote Desktop, a working NIC is imperative as the box will sit in a closet when finished.
I've tried putting in a Linksys NIC to see if there's some driver issues, but it acts the same way!
Any insight as to how to fix this issue is greatly appreciated.
Thanks,
~Travis W.
Sometimes, but not always - 3 out of 5 boots - the NIC doesn't start up with Windows. Win2K3 says that there is 'limited or no connectivity' through the adapter and I have to mess with the settings to get the NIC to work. (ie: disable/enable the NIC, renew IP, restart the system, etc etc) Since I'm trying to base the use of this machine over Remote Desktop, a working NIC is imperative as the box will sit in a closet when finished.
I've tried putting in a Linksys NIC to see if there's some driver issues, but it acts the same way!
Any insight as to how to fix this issue is greatly appreciated.
Thanks,
~Travis W.