Question Blocking ports in Firewall but nmap says otherwise

mangaman

Honorable
Jun 13, 2015
601
57
11,440
108
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
Jun 13, 2015
601
57
11,440
108

mangaman

Honorable
Jun 13, 2015
601
57
11,440
108
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.
 

mangaman

Honorable
Jun 13, 2015
601
57
11,440
108
Sorry for the ultra late reply.

The PID is 2724, which traces back to VMware Authorization service. So I'll leave that alone.

But what about the ports being open? Any way to set them as filtered?
 

ASK THE COMMUNITY