ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

problem with NIC

 
Ivakin Dmitry
Frequent Advisor

problem with NIC

Dear all,

My hardware is following: HP Proliant DL380 G4, NIC HP NC7782 Gigabit Adapter.
Software: Win 2003 SP1, Proliant Support Pack 7.91 (latest for today).
Problem: I install two windows patches, reboot server. After this I lost complely connection to the server.
Steps for solve problem: disable/enable NIC, unistall NIC and install again, assign other IP address, install new driver from Proliant Support Pack, change speed/duplex settings, did diagnostic tests (I found CPU test is failed but the same think on other server with operational adapter).
One strange think: if I ping the damaged NIC from my pc there is no connection. If I ping my pc from server the connection is OK.

Please give me some suggestions, how to solve it?
6 REPLIES
KarloChacon
Honored Contributor

Re: problem with NIC

Hi

are you using NIC Teaming?

check these articles
1. http://support.microsoft.com/kb/927695/
2. http://support.microsoft.com/kb/927168

regards
Didn't your momma teach you to say thanks!
Ivakin Dmitry
Frequent Advisor

Re: problem with NIC

Hello,

Thank you for your reply!

What does it means "teaming"? If you meaninig Teaming status - now it's "Not teamed".
But anyway, I followed to MS articles, changed registry information to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableRSS to 0 (it was 1 before) and reboot. Still bad result :(
KarloChacon
Honored Contributor

Re: problem with NIC

Ivakin Dmitry
Frequent Advisor

Re: problem with NIC

Yes, I can ping other computers from server. And no Internet.
I'll try your suggestions and let you you know then.
Ivakin Dmitry
Frequent Advisor

Re: problem with NIC

No helpful :(
1) Driver version has been updated
2) I have up-to-date firmware version, but overwrite it with just downloaded.

Some changes: I have Win2003 SP2
Ivakin Dmitry
Frequent Advisor

Re: problem with NIC

The problem has been solved by windows reinstallation. I install SP1 and the same patches. It's didn't happened again.