Discussion Locked

Event log filled with Compaq warnings

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

I have 3 Compaq NT Servers all connected to the same switch, two are fine, but on one the CpqNF3 network card has recently started filling the log with alternate 4105 Warning and 4106 Information events.

Every 30 seconds event 4105 (network cabledisconnect warning) is followed by 4106 (network is now okay) 2 seconds later.

The server itself seems to work fine and swapping cables and switch port connections does not have any affect.

I can find no record of this situation on Compaq or Microsoft's web sites.

Has anyone else seen this and know how to fix it, before I take more drastic action?

15 replies

by malcomblack40

I dont believe anything is wrong with the NIC as the Server is fine otherwise, also the on-board design makes me want to try other options first.

But thanks for helping.

by malcomblack40

I suspect the fact that the error code at the URL you supplied relates to network problems is coincidental, as the page is dedicated to errors from something called SequeLink ODBC, and my error is being generated by the NIC driver.

Also the warning occurs about every 30 seconds regardless of what the server is doing, even when it is idle.

Thanks for looking though!

by spydergst1

Get the latest compaq smartstart cd. I think its 4.9

Explore the cd. run the following command.

cpqsupsw\ntssd\setup.exe

Select the NIC card (the last item in the list) click the update button.

by malcomblack40

I already was using 2.19a and I dont think the LAN driver has changed since 2.18a. I download 2.20a, the latest version and that did not help either.

Thanks anyway.

by malcomblack40

I already was using 2.19a and I dont think the LAN driver has changed since 2.18a. I download 2.20a, the latest version and that did not help either.

Thanks anyway.

by mckaytech

I'm thinking that the NIC driver is reporting false network events, either because of a hardware failure or a driver bug.

We run 50+ Compaq servers and have found the Compaq Insight Agents to be invaluable in diagnosing problems of this type. There is a NIC agent that supplies a pretty comprehensive picture of what is happening with the NIC and it might be worth giving a try if you haven't already.

The other thought is that if it is connected to a managed switch, the switch itself might provide a clue as to whether the link is, in fact, dropping out every 30 seconds.

Finally, if you can borrow a Compaq NIC to pop in, you can bypass the onboard NIC and see if the problem still occurs. If not, your onboard NIC is flaking out and it may be the better side of valor to just install another NIC unless the system is still under warranty.

paul

by malcomblack40

Thanks, the switch is not managed. In the end I just disabled the o/b nic and installed a new NIC, fixed the problem but I still never found out why it was happening!

by winssuresh

1. If it is teaming NiC, apply the ssd's for NIC drivers after dissolving the team , click on each nic port and update.
Form the team once again and set the properties to 100/full or 100/half (as you normally use)
2.If the above doesnot work, click on team controller properties, uncheck heart beat.
This works well. But this works for intel nic cards.

by winssuresh

1. If it is teaming NiC, apply the ssd's for NIC drivers after dissolving the team , click on each nic port and update.
Form the team once again and set the properties to 100/full or 100/half (as you normally use)
2.If the above doesnot work, click on team controller properties, uncheck heart beat.
This works well. But this works for intel nic cards.

This discussion is closed to new replies.