M
M
MadWastefield2018-02-24 10:48:55
Wireshark
MadWastefield, 2018-02-24 10:48:55

Why does Wireshark on Windows 10 only catch incoming packets?

When pinging, wireshark only shows response packets (with a source address equal to the address of the pinged PC). No display or capture filters are set. What can be wrong?
This applies not only to ping, but to all traffic in general. If you filter like this: "ip.src == 192.168.1.2" where IP is the IP of this PC, which is listening, then not a single packet will be visible, that is, all packets caught are only incoming. In this case, if you catch using the Microsoft Message Analyzer, then there are packages with a source of 192.168.1.2.
I'm running as admin. The firewall is on, but I tried it with it disabled - the same result.
What can be wrong?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
M
MadWastefield, 2018-02-24
@MadWastefield

The case is open. But the verdict is not comforting. The culprit behind Wireshark's bad behavior is the COMODO firewall. I can draw such conclusions based on the fact that Wireshark fully earned ONLY after unchecking the COMODO driver in the properties of the network adapter.
Regrettable. We'll have to look for a replacement for Wireshark. Because a free replacement for COMODO has not been found to date.

1
15432, 2018-02-24
@15432

Remove installed nmap and reinstall wireshark

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question