Troubleshooting with Wireshark: Locate the Source of Performance Problems Laura Chappell
Publisher: Protocol Analysis Institute, Inc.

A very common problem when you launch Wireshark with the default settings is that you will get too much information on the screen and thus will not find the information you are looking for. Oct 5, 2010 - In today's blog post, I'm going to talk about an issue that I have come across several times while analyzing network traces with Wireshark. Note that it's well worth the efforts to spend some time working through the options provided as a wealth of information can be drawn from the capture set that can be instrumental in resolving a myriad of network issues including performance and security. Too much information kills the information. Sep 21, 2010 - On the Internet there are hundreds of excellent open source tools and utilities that can be used for network analysis, but not many technicians use th. Tried to find what hissing means, it's choppy audio? Anyway Capturing the ports on the source and destination and comparing the size? Let's take the following Time Source Destination Protocol Info. Oct 22, 2009 - Originally developed by Gerald Combs in 1998 and available as free/open source software under the name Ethereal, the project grew to encompass many programmers over the years and was renamed Wireshark in June 2006. Ideally I would like to see some sort of performance indicator that would prove the switches backplane capacity, ports etc is not the cause of the problem.