

- #NAME AT LEAST FIVE DIFFERENT SCANS THAT MAY BE PERFORMED WITH ZENMAP MAC OS#
- #NAME AT LEAST FIVE DIFFERENT SCANS THAT MAY BE PERFORMED WITH ZENMAP WINDOWS#
#NAME AT LEAST FIVE DIFFERENT SCANS THAT MAY BE PERFORMED WITH ZENMAP WINDOWS#
newer versions of Windows responding slowly and causing full-port scans to take much longer), I literally disabled all network interfaces on the system just after 20:52 last night. In order to eliminate the possibility that it was due to a weird host in the list (e.g. Then it started slowing down dramatically in terms of the estimated time to completion, without producing any additional results. It ran as expected for about an hour, and produced results for four of the hosts. Nmap -sV -p1-65535 -Pn -n -open -script= nfs -script=smb-enum* -script=smb-os* -script=smb-ls* -script=smb-server* -script=smb-system* -oA nmap-local_subnets-01-all_ports -iL hosts-02.txt The scan in question was against a list of 87 IP addresses, using the -iL option:

#NAME AT LEAST FIVE DIFFERENT SCANS THAT MAY BE PERFORMED WITH ZENMAP MAC OS#
I have a full process memory dump from the Mac OS version of nmap 7.70 that I can submit privately if it's helpful, but this is something I've observed with literally every version of nmap I've used since I got into security work about 7 years ago.

My workaround has always been to only run nmap against a single IP, with it run in a while read loop against a list of targets if I have more than one to scan, but I feel like this problem should be addressed in the tool itself. If there were a way to force it to output any results it's obtained to that point, it would be less of an issue, but I'm unaware of a way to do that. This has happened to me numerous times using the Linux and Mac OS builds. If I give nmap a set of multiple hosts to scan (using a network/mask, or a list of specific targets with -iL), there is a decent chance it will slow down dramatically and then effectively hang at about 99% completion. When I run nmap against a single host, it always completes. This is a persistent issue that I've run into for years, so I can't believe I'm the first person to report it, but I don't see an existing issue for it.
