Intel NIC always fails to reconnect after reboots

[waylo]

I recently purchased an Intel Gigabit CT PCI-E Network Adapter EXPI9301CTBLK from here http://www.amazon.com/gp/product/B001CY0P7G/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1

It has great reviews so I thought it'd be a no-brainer. I have a WinXP system which I am running as a HTPC and needed another ethernet port for my Silicon Dust HDHR Prime. I installed the proper most up-to-date drivers.

The problem is that after each and every reboot, the NIC completely fails to attempt reconnecting to anything it is connected to.

It will display as a 'network adapter unplugged' unless I disable and re-enable it. Or toggle some of the settings in the properties settings. Then it reconnects as expected.

I've tried setting the link speed to 1.0gbs full duplex, "wait for link" to on, and looked for any power saver options to disable. I've turned off 'reduce link speed during standby' and turned on every Wake on LAN option. None of these seem to do anything.

Any other suggestions? I'm aware of some command lines I could run as something automated after each boot to disable and enable the network adapter, but that's just jerry-rigging a problem that shouldn't exist to begin with.

 

[jwk3]

What kind of security or utility software do you have installed? some programs like Toshiba's control panel or Intel software suite software likes to hijack or override the usual windows settings.

The other problem is XP. it may still work for most things but the codebase is over a decade old (very old in computer terms) and more modern OSs will fare much better with new hardware.

 

[waylo]

I have the standard Windows firewall as well as Avast antivirus running. I'm not sure if they would interfere with the NIC detecting a cable plugged into it. Certainly they could alter how connections run through it, but that's not the case here.

My thoughts are turning toward some sort of power saving mechanism that is too robustly turning off the port but I wouldn't expect that to kick in right after a reboot.

Yes, XP definitely is showing its age and the OS on this machine probably will be retired soon enough.