Discussion Locked

Excessive receive errors detected on 3C9

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Nobody can't to login when server automatically start up (PWRCHUTE). Restart server helps, but it is not solution.
Is that message means that I should replace NIC (Network Interface Card)on my server, or what shoul I do??
Greets
LEON

9 replies

by hasse mcse/brainbench

Hi!

First I'd try to get the latest drivers and SP6a if this dosen't work I'd try and replace the NIC!

I take it by your PWRCHUTE comment that the NIC isn't working properly when the UPS starts up the server again after a power outage.

But if you then reboot the server again it's working properly.

I have no other suggestion than the above, never had this kind of error with Powerchute and UPS.

/Hasse

by duster52

Sounds to me like you may have mismatch duplex and speed problems with your NIC. I would check to make sure that the NIC is configured correctly after an automatic restart (PWRCHUTE) and after you manually restart the server. Check to make sure that the correct frame type, network number, duplex, and speed are getting loaded for that server. (I have since this type of error with some Intel NICs and some CISCO switches).

Hope this gives you a place to start looking.

by michael van den berg, cne5/mcse

If you didn?t make any changes to your fileserver or your network, AND the error came up when your server was up and running AND the problem came back after reboot, suspect a hardware problem. Maybe the 3Com.

But if you made changes, then undo that changes.
Came the problem up just after a reboot, why did you reboot? For an ABEND: do a VREPAIR. For activating changes: undo changes.

Also after reboot the problem can be that some autoconfiguration wasn?t occured properly, for exemple NIC speed/duplex. As mentioned by the previous answer. Also check you volume for errors.

Of course, for a stable system, have the latest patches and support packs loaded!

by kevin anderson

First, Get the latest drivers for the NIC.

Next patch the server to the latest Service Pack

What will probablly fix it though, is to down the server, and run a DOS program from on one of the driver disks that you made with the updated NIC drivers. There is a file called 3c90Xcfg.exe (Something like that, it's 3c???cfg.exe) anyways, run that, and set the duplex, and line speed manually. For some reason, the 3c980s seem to have problems with NWAY autodetecting connection types.

Kev.

This discussion is closed to new replies.