It could be something else, too. Have you followed Cisco's documentation on
identifying the source of these problems? They have some pretty good
documents on precisely this.
Frank
-----Original Message-----
From: wireshark-users-bounces@xxxxxxxxxxxxx
[mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Craig OBrien
Sent: Wednesday, May 06, 2009 12:15 PM
To: wireshark-users@xxxxxxxxxxxxx
Subject: [Wireshark-users] CRC errors at router
The FastEthernet interface on our cisco router is gathering input errors.
Generally at the rate that the CRC's errors are incrementing, it indicates
either a faulty application or speed negotiation issues with an internal
server or computer. But in not sure what,
Using wireshark, what would be the best method of capturing data on that
port so I can at least get a handle of what's doing these CRC errors?
Thanks
Craig O'Brien
Steen Outdoor Advertising / Big Mountain Imaging
(215) 334-1700 x166
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
