2 Intern

 • 

12.7K Posts

December 5th, 2006 00:00

You might look in device manager and do a properties on the nic in question and look for a power management tab and un tick the "allow this computer to turn off device to save power" box..
 
Also check any other power management settings also, check bios settings ect..
 
If all else fails, try the other NIC

20 Posts

April 4th, 2007 23:00

It's the Broadcom NetXtreme II NIC's.  They are known to be problematic with Windows Server 2003.  I ran into the same problem on a PE 1950, where I just could not get Active Directory to install.  I ended up adding in a Intel PCIe NIC to get around it.
There are instructions to follow to disable ToE on those Broadcom NIC's, which supposedly should fix the problem.  I followed them though, and still couldn't get the things to work right.
 
Do yourself a favor and get an Intel card.  I spent a week coming to this conclusion.

4 Operator

 • 

1.8K Posts

April 6th, 2007 17:00

"When I try to ping the server, it will have 100% packet loss for maybe 15-20 attempts."
 
I am assuming you Pathping the server.. are the losses  at the server card, not at the switch or any router?
 
Try driver directly from Broadcom
 
Have you run the diagnoistics...
 
Can you get this server off the net (off hours) so you can get a direct cable connection to another machine.
 
Have you hard coded the Speed/duplex settings, from lowest to highest?
 
If managed switch, have you tried hard coding speed/duplex on the port?
If managed switch, have you checked the ports for a buildup of errors? 
 
If you have Win 2000 machines, disable SMB signing on server/2000 wks
Checked power setting in the bios
 
"this problem only started happening after installing the new server." No, when Dell decided to use Broadcom.
No Events found!

Top