We used the product because it is the first tool used by everyone in security or networks during their initial stages. Everyone knows about Wireshark, its uses, and how simple it is for IT personnel to use it. It is easy to download, easy to configure, easy to look up, and easy to do anything. We don't have to rely on someone else to teach us how the product works.

My company uses Wireshark and has not tried a different solution. The biggest factor on why it decided to use Wireshark is because it's open-source software that doesn't require installation and a license, so anyone can use it.

I used Omnipeek. The UI was better than Wireshark. However, it is quite expensive.

If somebody pays for Omnipeek that heavy price, they also prefer to get a compatible adapter or a compatible card that works with Omnipeek.

In this company, people just use the solution. However, there wasn’t a discount moment when management suggested it to everyone.

I did not use another similar product before. 

I was working with Nmap and Cisco Analyzer, but then I started working with Wireshark. Before that, I used another packet analyzer called tcpdump, which is similar to Wireshark.

I have explored Microsoft Message Analyzer.

I also use MikroTik. It's easy because I've been working with it for years, so it's hard for me to compare it with Wireshark, which I only learned to make my YouTube videos and used a couple of times in the past. 

I'd say Wireshark and Nmap are more advanced and in-depth than using MikroTik by itself, but I haven't encountered a problem I couldn't resolve without using Wireshark. The exception is when a client doesn't have MikroTik, and they use a plain router or something like that. Obviously, I would need to pull out the other tools. MikroTik does what I need it to do. 

Previously, I used Microsoft Network Monitor but switched to Wireshark because it's open-source and richer in features.

I have used it more or less since 2001. So no, I did not use a previous solution.

No, we did not use another solution like wire-shark, but what we used in the past was the RADco. The RADcon was a protocol analyzer that was an all in one unit that was the standard at the time but did not allow for cooperative testing.

Sometimes I need to use tcpdump when I need to check the packets on CLI.

I used Microsoft's Network Monitor, but with due respect to Microsoft, I prefer Wireshark.