Recon scan does not trigger ping scan being disabled about nmapautomator HOT 3 CLOSED

this doesn't appear to be a bug. The host simply doesn't have any ports open, so the script can't run anything on it.
are you sure the host has open ports?

from nmapautomator.

Hi,

The host is up and has open ports, as I scanned it manually with the -Pn flag and 3 open ports were found (see original comment for command output)

The host does not respond to ping probes, but nmap automator doesn't recognise this for some reason. From looking at the source code it seems like it should display a message saying the host is not responding to ping probes, which doesn't show up in the terminal output.

Edit: I had removed which ports are open from my original comment as I'm not supposed to share those details, so it may have been hard to spot - but the number of open ports can be seen by the 997 filtered ports text (meaning 3 are open). Sorry for any confusion

from nmapautomator.

This same issue is occurring for me. I vote it be reopened.

If I run my port scan with sudo, SYN scan returns results.

from nmapautomator.