Question Blocking ports in Firewall but nmap says otherwise

mangaman

Honorable
I'm blocking ports in Windows Firewall, but when I run a loopback scan in Nmap, it says that the ports are open.

I go into windows firewall and create a new rule in the "inbound" section. I set it to "block the connection", then specify the port and protocol. I save it for public, private and domain, as well as giving the rule an easy to remember name and saving it. I do this for both TCP and UTP connections. Yet, nmap still detects the ports as open.

The nmap command that I am running is "nmap -T4 -A -v 127.0.0.1".

What is going on?
 
Last edited:

mangaman

Honorable

Ralston18

Titan
Moderator

mangaman

Honorable
Yes, I am establishing both an inbound and outbound rule.

Port number I am blocking is 1025, but it shows up in CMD netstat and NMap. I looked up the PID number in netstat and traced it to my services in task manager, under the service tab. However, no service is running under that PID.