Firewall Wizards mailing list archives
Re: RE: Sniffing out a firewall problem
From: Peter Lukas <plukas () oss uswest net>
Date: Sat, 3 Nov 2001 10:58:09 -0600 (CST)
Have each send a daily report of any of the following output: netstat -i You'll get some pretty useful stats. Typically, any system with Ierrs, Oerrs or Collis will be experiencing a problem. Check caples, duplex settings and of course, the card /switch port itself. Hardware's cheap enough these days to not warrant an ex(p|t)ensive investigation into the matter. Good Luck! Peter On Fri, 2 Nov 2001, Alan Young wrote:
That is the whole point, when you have 100 plus PC's to manage, I want to see quickly which IP number is creating all the problem before I spend hours tearing apart a bunch of machines.-----Original Message----- From: Thomas Ray [mailto:thomas.ray () tcud state tx us] Sent: Friday, November 02, 2001 9:39 AM To: firewall-wizards () nfr com; ayoung () veros com; aryoung () veros com Subject: RE: Sniffing out a firewall problem There is plenty of sniffer software out there that is free. But if you already know which NIC is causing this, why bother sniffing? just replace the card. that's the fastest way to fix it. if you have multiple NIC's in the box, replace one at a time until the problem goes away. if the NIC is giving you a broadcast storm, it's usually defective. it could also possibly be the patch cable too, so yes, it won't be easy to troubleshoot. how would I trblshoot it? -replace all patch cables if the problem goes away, you know the cause -replace NIC's one at a time if the problem goes away, you know the cause -if your problem still exists after doing the above, and you have a large network, it's time to start sniffing if you can't trace the problem to a specific system tomReply-To: <ayoung () veros com> From: aryoung () veros com (Alan Young) To: <firewall-wizards () nfr com> Date: Wed, 31 Oct 2001 09:46:25 -0800 Subject: [fw-wiz] Sniffing out a firewall problem. Hi All We have been experiencing a firewall failure due to a NICcard that isapparently chattering and creating an extremely high number of excessive collisions. What is the best way to debug this? We need to install a sniffer program on a PC somewhere, right? I have checked and sniffer software appears to be very expensive? Is there freeware that is available for Win32? This is definitely a job for the wizards. Alan R. Young_______________________________________________ firewall-wizards mailing list firewall-wizards () nfr com http://list.nfr.com/mailman/listinfo/firewall-wizards
_______________________________________________ firewall-wizards mailing list firewall-wizards () nfr com http://list.nfr.com/mailman/listinfo/firewall-wizards
Current thread:
- RE: Sniffing out a firewall problem Thomas Ray (Nov 03)
- RE: Sniffing out a firewall problem Alan Young (Nov 03)
- Re: RE: Sniffing out a firewall problem Peter Lukas (Nov 03)
- Re: RE: Sniffing out a firewall problem Ryan Russell (Nov 04)
- RE: RE: Sniffing out a firewall problem Robert McMahon (Nov 05)
- RE: RE: Sniffing out a firewall problem Chiman (Nov 06)
- RE: RE: Sniffing out a firewall problem Anton (Nov 13)
- Re: RE: Sniffing out a firewall problem Pierre-Yves BONNETAIN (Nov 09)
- Re: RE: Sniffing out a firewall problem Peter Lukas (Nov 03)
- Re: RE: Sniffing out a firewall problem Peter Lukas (Nov 05)
- RE: Sniffing out a firewall -SNORT blew up registrty Chiman (Nov 06)
- RE: Sniffing out a firewall problem Alan Young (Nov 03)
- <Possible follow-ups>
- Re: RE: Sniffing out a firewall problem TDyson (Nov 03)
- Re: RE: Sniffing out a firewall problem Gregory Hicks (Nov 05)
