Sniffer question

 i have a client that is complaining of slow network traffic. he thiks he has a bad line or a chatty nic. I am not familure with sniffers. what is a good one to download, and any help using would be great. Than kyou in advance
Who is Participating?
fixnixConnect With a Mentor Commented:
eberhardt2329 :

You could send the ethereal log to me if you want, but I probably won't get the chance to look at it until the weekend.  Send to wedgenix at if you want me to take a look when I get the chance.

You can get a little more features and ease of use -- for awhole lot of cash....

Note:  If it's only one user, try replacing his network cable.  CAT5 isn't as tolerant of abuse as many people seem to believe....

eberhardt2329Author Commented:
it seems to be the whole place web traffic moving files etc. the two I sent to the user are, and                and I want them to run for a hour each, and send me the files. Any ideas?
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Unless you filter out a lot during the capture (which could be confusing to a new user of Ethereal, see for a good page on filtering syntax and examples) you definately don't want to capture for an hour.  On a 5 computer LAN segment here, a 5 minute promiscuous capture yields a log file that is painfully slow to sort, manipulate, poke around, and use on a (slow, 1GHz, 128ram) workstation.  On a decent machine 5 mins wouldn't be a problem, depending on your typical network activity and number of workstations, but an hour would just be too much to work with right off the bat.  Capture everything for about a minute or two and have a look.  Hopefully you'll see errors and can set up capture filters honing in on said errors for a longer duration capture if necessary.
Microsoft network monitor isn't bad,  but is extremely difficult to make expert analysis with these tools. In general much better solution is to use managed Switches which are able detect problems on network layer, and sniffers can be used to solve problems L3 layer.
It's the whole place?
This could be any number of issues... slow backbone (10 MBps on a heavily used network can hurt). It could also be slower at different times of the day of a lot of users are playing around, logging in, (morning, lunch) etc... What kind of pipe do you have coming into the area from the outside world?
eberhardt2329Author Commented:
I believe they have a t1. I have saved the log file from the sniffer, can I sent this to someone not sure how to put this on here I am using ethereal
In order to address the real problem... "Why is network traffic SLOW",
I believe we need to know alittle more about the network.  

Do you know the network layout including hubs, switches, number of clients on each node, etc.

Is the traffic slow to the internet or to other clients within the network or both?

Did this problem happen over time or all at once.  over time could indicate too many clients connected thur too many hubs.  Too many hubs on a large network will slow traffic to a crawl.

Solution would be to replace hubs with switches in key places.
If it happened all at once, this means something may have broke.  ie, bad cable, chatty NIC, whatever.

If it is a chatty NIC it should only affect that particular node (clients connected directly thur hubs) and not the entire network.  

If it is a bad cable it will only affect either the internet access and not intranet traffic, or visa versa.

So the question is...
is it the entire network that is being affected or just a section?
When and how did the problem start?
Why does the customer believe it is a chatty nic, he may have more information about the problem than he has said.

oh, and btw, with a sniffer, it will only capture packets that it is directly connected to.  
in other words.  if you want to just sniff the packets from a single computer put the sniffer on that computer, if you want to see a section of the entire network, you have to connect the sniffer to a hub on that network(NOT a switch).  A Sniffer will not see traffic on another port of a switch except for broadcast traffic within a subnet.  

Even if it's a t1, it could just be normal network traffic sucking the life out of the wires. My building is runnning on fiber and I'm connected to a gig backbone.... we have a 9 Mbps pipe to the outside world, but it's slow sometimes. Like I said before, any number of issues could come into play, even if things are working normally.
try to use packetyzer... its a freeware you can download at
Since everyone has already mentioned my favorite remote analysis tools, have you tried just going into the network closet, looking at the switch, and watching which port(s) are lit up all the time?


eberhardt2329Author Commented:
I have not been on site, does anyone know where I can download sniffer plus I like the interface. thank you any other ideas woiudl also be great
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.