> Your NIC firmwares Yep, that eventually did the trick, though there were some caveats: somehow when applied, the firmware update only updated one NIC. The other one (the one on the team) remained with the older version. Obviously the team went down as soon as the server got restarted. As soon as I re-run the update, both NICs got the latest firmware. You can check the firmware version of each NIC on the Broadcom utility. Thanks for advise.
Hi guys, I have a couple of T300 servers (Windows 2008 Server x86 - SP2), which are preforming pretty mundane tasks (AD, DFS, WSUS, Print Server). Both servers have the Broadcom Advanced Control Suite driver (14.4.2.2) installed on them, and, until recently, had a team (load balancing&failover) created using the two physical NICs. They had been operating without a glitch thourhgout the last two years until I decided to install Dell Openmanage application (6.5.0). As soon as OpenManage is installed, both servers lost all contact with the network; I couldn't even ping them. I had to go onto the physical console and dissolve the team. Once you "mingle" with the team settings, both the team and the independent NIC come back to life and start working again. That is until you reboot the server. Once rebooted the team will work for a few minutes (though very slowly) and ultimately will go quiet. The only way to have the server come back to life is, once again, mingleing with the team through the console. At first, I thought this was an MS patch issue, but I have been able to replicate the problem on two indentically configured, independent servers. I took a long look at the openmanage documentation, but there are no compatibility warnings between the openmanage & the BACS drivers. I am out of ideas, but to open a ticket with Dell. anybody here has experienced a similar issue? Thanks 
Openmanage and Broadcom teaming issues?