BLOG

By Betty DuBois 12 Jun, 2017

Sometimes people think that using a tool like Wireshark will fix their network.  I hate to be the bearer of bad news, but it won’t.  If at any point in your network’s lifetime, someone hooked up some type of “sniffing” device and said, “Well there’s your problem right there”, you may have fallen under the impression that the sniffer “fixed it”.  Sorry, it was the experience and education of the person who was using the tool.   Not the tool itself.

Network analysis takes time and practice.  You have to be in the right place, at the right time, capturing the right data before you can even get started.  There are ways to become more efficient, and to capture more data, but you still have to know how the application is supposed to work before you can look for what is wrong.  Take the time to learn the protocols, how things look when they are working, how to filter like there is no tomorrow, what the dependencies are, and what the physical path of the data is for the application.  Then perhaps you too will be able to fire up Wireshark and say, “Well there’s your problem right there”.


By Betty DuBois 12 Jun, 2017

Sometimes people think that using a tool like Wireshark will fix their network.  I hate to be the bearer of bad news, but it won’t.  If at any point in your network’s lifetime, someone hooked up some type of “sniffing” device and said, “Well there’s your problem right there”, you may have fallen under the impression that the sniffer “fixed it”.  Sorry, it was the experience and education of the person who was using the tool.   Not the tool itself.

Network analysis takes time and practice.  You have to be in the right place, at the right time, capturing the right data before you can even get started.  There are ways to become more efficient, and to capture more data, but you still have to know how the application is supposed to work before you can look for what is wrong.  Take the time to learn the protocols, how things look when they are working, how to filter like there is no tomorrow, what the dependencies are, and what the physical path of the data is for the application.  Then perhaps you too will be able to fire up Wireshark and say, “Well there’s your problem right there”.


Share by: