Ethereal-users: Re: [Ethereal-users] Spotting a bad nic?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Tom Greaser" <tgreaser@xxxxxxxxxxx>
Date: Sun, 01 Feb 2004 19:10:21 -0500
If ethreal does allow you to caputure bad frames then you should see crc
errors on the frame..
This is somewhat normal..(shouldnt happen to much)

Your problem is probably up the stack.. layer 3 or 4

What protocols are you using ??? 
Are these machines connected to the internet ???


Years ago i had issues with software on an IPX network getting bad data
causing systrems to lockup.. 

hope that helps.


       .~.
       /V\      
      //   \\    
     /(     )\   
      ^`~'^
~~~~~~~~~~~~~~~~~~~~~~~~~~
Tom Greaser  
Red Hat Linux Certified Engineer
Senior Network Engineer
Information System Operations
Health Sciences Center

Phone 304-293-4683
FAX     304-293-7268

tgreaser@xxxxxxxxxxx
>>> "reg burns" <rburns@xxxxxxxxxxxx> 02/01/04 6:24 PM >>>
I'm sort of troubleshooting a windows me network for someone.  All the
machines on the network randomly lock up, though I've noticed that
transferring data on the network seems to trigger the lockups.  I've
swapped
out switches and all nics use the same driver which I'll be updating,
but it
is possible that a bad nic or cabling somewhere would be causing this? 
If
so, how do I spot a bad nic with ethereal on a switched network?  Should
the
data just look like garbage or do I need to look for something?  Will
the
source IP still be legible so I can spot the culprit?