3Com Hub Problem

Our company maintains over 1000 managed 3Com 3C16406 24-port 10BaseT shared hubs and have for a few years now.  They have worked very well for us but since last Friday (09/14/2001), random hubs on different subnets in different buildings more than likely under different traffic loads have stopped answering pings.  The users on the hubs seem to be working fine but the IP management on the hubs won't answer to pings.  Power cycling the hubs fixes the problem.  Telnet and web access is disabled on all of the hubs.  Only SNMP and console access is enabled.  Have there been attacks that other network engineers have noticed in the last 5 days or so that are similar to what we are seeing??
Who is Participating?
contrazoomConnect With a Mentor Commented:
Hmm, I think you have been infected by the code red worm. Disable port 80 and see if 3Com has a bug fix available.
Kind Rgds
dekkybAuthor Commented:
From looking at sniffer traces, it appears that our hubs are being hit through port 80 by machines infected with a couple different viruses.  The problem is that even though we have port 80 disabled on the hubs and even though port 80 won't accept access to the hub management, the port still acknowledges that it was probed.  Therefore, when it gets hammered from an infected machine, it blocks the entry but replies with an acknowledgement which still takes away bandwidth from the hub until the hub management finally gets confused to the point of no return.  Is there a way to truly cause port 80 on the hubs to turn a deaf ear to port 80 probes and hence not even reply with an acknowledgement? That would probably fix our problem.
dekkybAuthor Commented:
I believe we are also being hit by the Nimda virus but...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.