ProLiant Servers - Netservers

Network card not responding

 
SOLVED
Go to solution
SB Jason
New Member

Network card not responding

Hi,

We have a ML370 with windows 2003 server and the network card stopped responding. To solve the issue, we had to reboot the server. The system event log had some events from l2nd and tcpip.

This happened on a remote server so the system logs I have don't have a proper description for the l2nd events. They had event id 4 and 11. Looking at http://www.eventid.net/display.asp?eventid=4&eventno=9208&source=l2nd&phase=1 it seems to be an issue with enabling both nic cards. Does anyone have a list of the error codes and what they mean please?

For the tcpip event we had event ids 4201
(The system detected that network adapter HP NC373i Multifunction Gigabit Server Adapter #2 was connected to the network, and has initiated normal operation over the network adapter.) and event id 4202 (The system detected that network adapter HP NC373i Multifunction Gigabit Server Adapter #2 was disconnected from the network, and the adapter's network configuration has been released. If the network adapter was not disconnected, this may indicate that it has malfunctioned. Please contact your vendor for updated drivers.)

The latest network drivers on this site are from 2006 so we are up to date.

Has anybody else come across this? Is this likely to be a hardware fault?
2 REPLIES 2
Kedd Guyton
Respected Contributor
Solution

Re: Network card not responding

The ML370 G5's NC373i driver was updated a couple of weeks ago. The NC373i is the Broadcom Multifunction device:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3279719&prodTypeId=15351&prodSeriesId=1121474&swLang=8&taskId=135&swEnvOID=1005

You may need to disable the Scalable Networking Pack which is enabled by default in Windows Server 2003 SP2:
http://support.microsoft.com/kb/948496/
SB Jason
New Member

Re: Network card not responding

Thanks for the reply and the link to the latest drivers. I don't know if this is the problem but the MS KB article sounded like what we had and we'll try the updated drivers.

Cheers.