Firewall - port closed despite inbound rule

Hello,

First of all I have to apologize for my bad English. I've experienced a strange issue with the Windows Firewall. I tried to open port 6881 for inbound traffic and created an inbound rule for every profile that should allow any IP to send TCP and UDP traffic to my local port 6881. I also activated the firewall logging for every profile.

Unfortunately the port checking websites state that port 6881 is filtered. My first thought was to check the log if the the packet was being dropped but there was no traffic for port 6881 in the log. After that I disabled the firewall and started the test again. Now the port checking website told me the port was closed (not filtered, because there was no service listening to this port). It seems to me that the firewall totally ignores the traffic or the inbound rules I've created, but leaving the firewall off is not an option. Do you have any ideas? Thanks in advance!

Edit: Ping requests are logged properly but not the request for the specific port.

April 24th, 2015 3:33am

Hi,

Typically we dont suggest testing port state by using these website because it has lots of requirements such as pushing host machine to external environment to get external IP address without gateway, external firewall or ISP affect.

Regarding to this kind of issue, it is possible that the 6681 port has been filtered by other rules, when rules conflict occurs deny rules will overwrite the allow rules by default.

And please try using command such as telnet check the port state instead of these websites, if this port is used to binding specific program/service, using these programs for test will always be the best option.

Regards,

D. Wu

Free Windows Admin Tool Kit Click here and download it now
April 27th, 2015 10:38pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics