NMAP all ports are in ignored state

1

Hi guys, I have a problem with Nmap.
When I scan:

nmap (different stuff like -sV -Pn) +ip

The scan complete with 1000 ports scanned but in ignored state(conn-refused).

I search on the web but nothing resolve this, do you know why? Or do you have a good alternative to nmap?
Thank you!

2 Likes
2

It signifies that although Nmap was able to finish a TCP handshake with the target system, the target system actively refused the connection when Nmap states that a port is in the “closed” or “conn-refused” state. This could indicate that no service is listening on that port or that the target system’s firewall is preventing the connection.

Ports that are deliberately excluded from the scan using the “—exclude-ports” option or by the target system’s firewall preventing the connection are referred to as being in the “ignored” state in Nmap, which does not provide any information about the port’s status.

It’s likely that some of the ports Nmap lists as “ignored” are truly closed or filtered; however, Nmap was unable to ascertain their status because of the scan settings chosen or the target system’s network configuration.

You can experiment with various Nmap scan options and approaches, such as UDP scans or version detection (-sV) to identify certain services operating on the target system, to gain a deeper understanding of the target system’s network topology and services. To learn more about the target system and its services, you can also try using additional network reconnaissance tools.

3 Likes
3

Ok, thank you so much! I try with other filters.

4

I have the same issue, the vpn is correctly setted i can ping the machines but when I try to nmap the ports are in ignored state, I tried to change the network interface of the vm and I tried to disable my gateway firewall but nmap still doesn’t work. Did you manage to solve it?

5

were you able to solve it because i have the same issue…

6

An answer to a similar question has been outlined here

Try using: nmap --reason -dd

7

Any possible solution to this problem?

8

did you manage to solve it?

9

I have same problem when scan the machine at stating point “Redeemer” .
I think the problem in “Redeemer” machine

1 Like
10

I’m also having the same problem with Redeemer, maybe it is exclusive to Redeemer but I’m still convinced we’re doing something wrong

11

I had the same issue, I was using parrot os on an vm but live, after i installed parrot on the vm i had no issues.

12

I have this problem with this machine too (Redeemer). I think that it has a problem. Use the next command pointed in the ‘walkthrough’ and continue the machine

13

You can speed up the scan by using the following command, as the default process is quite slow:

nmap -p- 10.129.88.30 --min-rate 5000 -v
14

I found a solution using the -Pn flag to disable host discovery since we’re just scanning for open ports. Additionally, use the --min-rate option because the scan will be extremely slow without it.

sudo nmap -p- -Pn redeemer.htb --min-rate 10000 -v

15

I’ve encountered similar problems too