When I specify an individual target,

>nmap -v3 -sn

I get the correct and expected nmap response

Starting Nmap 7.70 ( https://nmap.org ) at 2019-11-08 11:16 India Standard Time
Initiating Ping Scan at 11:16
Scanning [2 ports]
Completed Ping Scan at 11:16, 1.00s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 11:16
Completed Parallel DNS resolution of 1 host. at 11:16, 5.62s elapsed
DNS resolution of 1 IPs took 5.62s. Mode: Async [#: 4, OK: 1, NX: 0, DR: 0, SF: 0, TR: 3, CN: 0]
Nmap scan report for raspberrypi-dQ2XyAPpB6.dhcp.XXXX.com (
Host is up, received conn-refused (1.0s latency).
Read data files from: C:\Program Files (x86)\Nmap
Nmap done: 1 IP address (1 host up) scanned in 6.70 seconds

However, when I specify a range,

>nmap -v3 -sn 172.18.184,186,188.0-255

I get,

Nmap scan report for YYYY.dhcp.XXXX.com (
Host is up, received syn-ack (0.0010s latency).
Nmap scan report for [host down, received no-response]
Nmap scan report for [host down, received no-response]

I'm running Windows 10 version 1809 build 17763.737 and Nmap 7.70

Additional info if it helps

>nmap -version
Nmap version 7.70 ( https://nmap.org )
Platform: i686-pc-windows-windows
Compiled with: nmap-liblua-5.3.3 openssl-1.0.2n nmap-libssh2-1.8.0 nmap-libz-1.2.8 nmap-libpcre-7.6 WinPcap-4.1.3 (packet.dll version 10 nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: iocp poll select

Is this a bug, or am I missing something in the switches ?

Thanks !

1 Answer 1


Have you tried upgrading to Npcap instead of WinPcap? Nmap comes bundled with it, though you can and should get the latest stable and bug-free version from https://npcap.org/#download . It is faster than WinPcap and designed for modern versions of Windows, so you should be less likely to see problems like lost packets.

Your Nmap is also out-of-date, though only by 1 release. I'm not aware of any specific bugs that would be causing that behavior, but our advice is always to upgrade before making a bug report in case the issue is solved in a later release.

  • 1
    The upgrade to Nmap 7.80 and Npcap-0.9984 works great now. This issue was so trivial that I was thinking this is probably some error on my part.
    – R S
    Nov 11, 2019 at 7:33

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .