View Single Post
11 Oct 2011  

Windows 10 Pro x64

Ah - OK, so I understand. Generally, wireshark uses WinPCap on Windows, which is a protocol driver. It's actually inserted first in the NDIS stack, meaning it will see traffic destined anywhere on the system, even the windows filtering drivers (where the firewall gets a crack at packets). If you aren't seeing anything with WinPCap installed, the problem is not the firewall, it's more likely a driver issue (as that's where the WinPCap driver sits in relation to everything else - sounds like WinPCap is either not getting informed of the packet coming in, or it's not doing what it's supposed to with it when it does). Does netmon 3.4 see data in this same situation? Netmon sits *above* the filtering engine, so if it sees it, you can be absolutely certain it's not a firewall issue.
My System SpecsSystem Spec