If it's a physical layer problem, a sniffer will not help you. A device
like a Fluke would do the job. The first place to start is testing the
cable. If that tests ok, then check the duplex settings on both end
devices. Make sure they are hard coded for the apprpiate setting, not set
to auto negotiate. If both devices are configured properly, then you need
to start looking at the individual hosts and of course the sniffer would
work fine. Maybe there is a bad NIC? Bad patch cable? Or a corrupt
driver?
""Kevin Wigle"" <[EMAIL PROTECTED]> wrote in message
00e501c09d21$b10bdc40$[EMAIL PROTECTED]">news:00e501c09d21$b10bdc40$[EMAIL PROTECTED]...
> Group,
>
> There are a few sniffer users on the list and I got a question.
>
> I'm using Net Xray, Sniffer Pro is available (but not installed yet).
>
> We have a problem of out of order packets and just recently I've noticed
on
> the router console that we're getting late collisions.
>
> Now I always thought that late collisions were a product of a cable that
is
> too long. In this case however, it's fibre from the basement up to a lab
to
> a foirl and then a patch cord length of 10BaseT from the foirl to the
> router.
>
> I'm looking at the sniffer output and I don't know what to look for to
> identify late collisions. I don't even know if you can see them or the
> symptoms with a sniffer.
>
> Can anyone (even if you watch other lists.... :-) ) comment if the
> sniffer is even a viable tool to troubleshoot this?
>
> I've been going at it with our ISP for some time now and I need some
> ammunition to get them to do something.
>
> Kevin Wigle
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
