Windows Update for Intel GB adapter crashing ML370

Yesterday I ran windows update on an ML370 running Windows 2000 server.
An update for the Intel 10/100/1000 dual port adapter showed up so I
downloaded the update and rebooted. After rebooting and getting to the
login screen the server froze. I rebooted again and this time the
adapter was not working (I was logged in using a remote insight card).
Ran ipconfig and it showed no IP address bound to the adapter. So I
stopped and restarted the adapter and the IP address finally appeared.

Today I logged in again, remotely, as I wasn't feeling to good about
what had happened yesterday. After logging in through remote desktop,
I double clicked on the green Intel ProSet icon and proceeded to loose
my remote desktop connection. Logging in again using the remote
insight card revealed the computer had actually blue screened. Power
cycled the system and it came back up and is running at the moment, but
I'm afraid to do anything else at this point as it's an Exchange server
and I feel lucky at this point to not have a corrupted database.

Has anyone else run into anything similar to this? I don't know if the
issue only exists on Compaq servers or all servers using this NIC.

Never, never, NEVER use windows update to install device drivers on an
Comap/HP server. Just dont do it. Ever !

Get your drivers from HP thought the sofware and driver downloads, or use
the Proliant Support Pack.

- LC

On 5 Sep 2005 17:16:23 -0700, Jesse wrote:

Yesterday I ran windows update on an ML370 running Windows 2000 server.
An update for the Intel 10/100/1000 dual port adapter showed up so I
downloaded the update and rebooted. After rebooting and getting to the
login screen the server froze. I rebooted again and this time the
adapter was not working (I was logged in using a remote insight card).
Ran ipconfig and it showed no IP address bound to the adapter. So I
stopped and restarted the adapter and the IP address finally appeared.

Today I logged in again, remotely, as I wasn't feeling to good about
what had happened yesterday. After logging in through remote desktop,
I double clicked on the green Intel ProSet icon and proceeded to loose
my remote desktop connection. Logging in again using the remote
insight card revealed the computer had actually blue screened. Power
cycled the system and it came back up and is running at the moment, but
I'm afraid to do anything else at this point as it's an Exchange server
and I feel lucky at this point to not have a corrupted database.

Has anyone else run into anything similar to this? I don't know if the
issue only exists on Compaq servers or all servers using this NIC.



Does Windows 2000 allow you to "roll back" a device driver installation?
I know that Windows 2003 allows you to do that.

If not, download a new driver from HP or the Intel Web site.

A Microsoft driver might not support the Intel ProSet utility.

Aidan Grey

If he is using an HP adapter (even if it has an Intel chipset), he should
not be using the ProSet utility for teaming, etc. He should be using the
Network Configuration Utility v8, which can be found under the Network
Software section of the Drivers and Software support site for that model of
server.

If he is using an Intel branded card, he should use theh Intel drivers for
the adapter from the Intel Site. It is then acceptable to use the ProSet
tools ... if this is the case.

- LC

"Aidan Grey" wrote in message
k.com...
On 5 Sep 2005 17:16:23 -0700, Jesse wrote:

Yesterday I ran windows update on an ML370 running Windows 2000 server.
An update for the Intel 10/100/1000 dual port adapter showed up so I
downloaded the update and rebooted. After rebooting and getting to the
login screen the server froze. I rebooted again and this time the
adapter was not working (I was logged in using a remote insight card).
Ran ipconfig and it showed no IP address bound to the adapter. So I
stopped and restarted the adapter and the IP address finally appeared.

Today I logged in again, remotely, as I wasn't feeling to good about
what had happened yesterday. After logging in through remote desktop,
I double clicked on the green Intel ProSet icon and proceeded to loose
my remote desktop connection. Logging in again using the remote
insight card revealed the computer had actually blue screened. Power
cycled the system and it came back up and is running at the moment, but
I'm afraid to do anything else at this point as it's an Exchange server
and I feel lucky at this point to not have a corrupted database.

Has anyone else run into anything similar to this? I don't know if the
issue only exists on Compaq servers or all servers using this NIC.



Does Windows 2000 allow you to "roll back" a device driver installation?
I know that Windows 2003 allows you to do that.

If not, download a new driver from HP or the Intel Web site.

A Microsoft driver might not support the Intel ProSet utility.

Aidan Grey