Network dropping out on startup - PowerEdge T300

Question

Hi everybody: I recently did a fresh install of Windows 2008 Server R2 on our PowerEdge T300 server. We have the dual Broadcom 5722 chipset NIC's onboard. When I boot the server up and it stops at the login screen, I can ping the server for about 15 seconds. Then, all of a sudden, it becomes unresponsive - cannot ping by hostname or IP address. When I log in, the 'limited availability' icon is displayed. Here's what I've tried thus far: 1. I tried switching from one NIC to another. No help. 2.  I tried having only one NIC enabled (other is disabled).  No help. 3. I updated the drivers for the Broadcom chipset. No help. 4. I disabled the power management functions on both adapters. No help. 4. I installed the Broadcom utilities, and teamed the two adapters up to work as a virtual adapter. No help. 5. Tried uninstalling and reinstalling the drivers. No help. 6. I had Symantec Endpoint client installed on the server (antivirus and spyware only). Thinking that might be a problem, I uninstalled that. No help (Symantec Endpoint Manager is still running, however) 7.  Tried a different network interface cable.  No help The only way I can correct the problem is to go into the network adapters, disable them and re-enable them. Then, they work fine until the server needs to restart again. Then, the problem starts all over again. If I look at the back of the server, the NICS are both blinking rapid amber when I'm having trouble with connectivity. After disabling and re-enabling, they blink intermittently as is normal. I don't think the NIC's are bad. I could see perhaps one being bad, but because the behavior is happening on both of them, that tells me that there's most likely another cause. Under Windows Server 2003, we didn't seem to have any problems. Has anyone come across this issue or might be able to suggest a fix? I'm stumped as to what to try next. Thanks everyone!

DELL-Chris H · Answer

Rcpwisc,

It sounds like it maybe a driver and firmware issue. Have you run the DUP (Dell Update Package) for the NICS yet, also have you updated the firmware as well?

The update package can be found here - http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/poweredge-t300?driverId=HXVWW&osCode=WS8R2&fileId=2731093564&languageCode=EN&categoryId=NI

This the Broadcom firmware update - http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/poweredge-t300?driverId=P32M4&osCode=WS8R2&fileId=3230162484&languageCode=EN&categoryId=NI

Let me know how it goes.

RCPWISC · Answer

Thank you very much for the quick reply. As of right now, I'm running version 15.6.0.10 (06/04/2013) from Broadcom's web site (http://www.broadcom.com/support/ethernet_nic/netxtreme_server.php). I see that the driver you provided for me is version 14.2.0 (07/06/2010). The firmware link, however, is version 7.6.15 (07/02/2013).

Is it possible that the drivers I'm running now (v15) require the firmware update? I'd like to try and keep the driver I have as the one you provided doesn't support the teaming option, and I'd like to try and keep that for redundancy purposes.

Thanks for your continued assistance.

DELL-Chris H · Answer

If the firmware is that far back it can cause issues if you have the most current driver and not keep the firmware current as well. I would start with the firmware update and go from there.

RCPWISC · Answer

OK, great!  Will give that a try and see if it works.  How do I upgrade the firmware BTW?  Is it an executable file that I simply run, or do I need to create a special boot disk to perform the upgrade?  Thanks again!

RCPWISC · Answer

That seems to have done the trick!  Though - when I log in, the network icon appears with a red x through it.  It takes about 2 minutes before the icon changes to indicate network and internet access.  I had issues with this on some Vista workstations as well, so I'm assuming that it's more of an interface problem than anything else.  All I care is that it's working, and I'm grateful to you for your help!!  :emotion-2:

VSammons · Answer

I am having the same issue but it is running Windows 2003 R2

PowerEdge Hardware General

Was this post helpful?