Windows firewall doesn’t work

Posted on

QUESTION :

I’ve added a rule to Windows firewall to block all incoming connections on port 80:

rule

But it has no effect – CurrPorts shows apache listening on port 80 and also nc (ncat on Win) shows port is still open.

ANSWER :

I’ve added a rule to Windows firewall to block all incoming connections on port 80

But it has no effect – CurrPorts shows apache listening on port 80 and also nc (ncat on Win) shows port is still open.

You are using the wrong tools to determine whether the Firewall is doing its job.

CurrPorts and nc/ncat are showing listening ports.

That means there is a program listening on port 80. It does not mean traffic can actually reach that port.

You can run a program listening on any port and it can just sit there doing nothing at all.

Try using telnet (from a different PC).

Windows:

telnet ip_address 80

Unix:

telnet ip_address:80

If the Firewall is working you will get the response “timeout”.

Leave a Reply

Your email address will not be published. Required fields are marked *