This issue is likely related to how macOS handles privilege escalation for certain Nmap operations. Some advanced Nmap features (such as OS detection or vulnerability checks) require root privileges to function correctly. If Network Scanner is run as a regular user, those Nmap calls may silently fail or return no results.
To resolve this, try launching Network Scanner with sudo from the Terminal:
sudo /Applications/Network\ Scanner.app/Contents/MacOS/netscan
When launched successfully, you should see
[root] in the window title bar, indicating that Nmap will also be executed with the necessary privileges.
Additionally, the
latest version of Nmap has a known issue on macOS when run as root, which may cause it to return no output at all.
As a workaround, open Nmap Settings and add the following line in the
Custom command line parameters field:
--disable-arp-ping
This disables the problematic ARP ping phase and allows the rest of the scan to proceed as expected.