I stopped Windows 7 Firewall in
Services, but it (or one of its minions) is still dropping packets.
I am trying to use
rtiddsping (custom ping for the DDS framework I'm using) to debug a DDS communication problem between two Windows machines. The machine that should be receiving the ping drops them with the message "The Windows Filtering Platform has blocked a packet" showing up in the Event Viewer.
I stopped Windows Firewall Service, but the packets still get dropped. I can see the blocked packets in Wireshark on the receiving machine. What's going on? What am I missing? Is
Windows Filtering Platform something separate? I don't see it running in
In response to @Frank below, yes, I have tried enabling the firewall and creating rules to allow the programs I desire. See picture below.
In response to @ernie below, here are two screenshots from the Event Viewer with DDS Spy off. Notice it disallows both the inbound packet and the inbound connection.
Update: In response to @ernie in the comments below, I created a DDS application that publishes and subscribes on the same computer to see if WFP is working as designed and the DDS middleware is simply dropping the packet.
With the same computer publishing and subscribing, I did not see any blocked DDS packets in the Event Viewer and messages got through as expected. I think that when the Event Viewer says "The Windows Filtering Platform has blocked a packet" it means the packet stops there and does not get routed on.
Why are these packets are being blocked by WFP?