Skip to content

Troubleshooting

knoxxr edited this page Jul 14, 2026 · 1 revision

Troubleshooting & FAQ

ICMP ping is blocked / hosts show as Timeout

Depending on the Linux/macOS setup, ICMP ping may be restricted for a normal user. When a permission problem is detected, the affected host is treated as no-response (Timeout) and a guidance message is logged once, so the scan is not interrupted.

  • Linux: grant just the ping capability with sudo setcap cap_net_raw+ep <path-to-executable>, or run with sudo.
  • macOS: usually works without extra permissions; if restricted, run with sudo.

MAC address / vendor is empty

ARP (MAC) lookup uses the SendARP API on Windows and parses the system arp command on macOS/Linux. On Unix-like systems the lookup only works after the ARP cache has been populated by a ping to that IP. The scan always pings first, so normal use is fine — but a host that never answered ping may not have a MAC resolved.

"Windows protected your PC" (SmartScreen)

The installers are not code-signed yet, so SmartScreen may warn on first launch. This is a false positive: click More info → Run anyway.

macOS: "NetworkScanner-osx-Setup.pkg can't be opened"

The .pkg is not notarized yet. Either:

  • right-click (Control-click) → Open in Finder, then Open again in the dialog, or
  • run xattr -d com.apple.quarantine NetworkScanner-osx-Setup.pkg in Terminal, then open it.

Antivirus (e.g. AhnLab V3) quarantined or deleted the installer

Because the unsigned installer bundles an auto-update mechanism (Velopack), some antivirus products mistake it for a suspicious pattern and quarantine it without scanning. It is not malware. You can:

  • restore the file from the antivirus quarantine and add it to the scan exclusions,
  • download the Portable (zip) build (no installer / auto-update behavior), which is less likely to trigger a false positive, or
  • report the false positive to the antivirus vendor so future builds are recognized.

The real fix is a paid code-signing certificate, deferred for now on cost/priority grounds.

FTP password isn't being remembered / warning about Base64

The password is stored in the OS credential store (DPAPI / Keychain / libsecret). If the required tool is missing (e.g. secret-tool not installed on Linux), it falls back to Base64 obfuscation and logs a warning. Install the credential tool for proper encryption. See Configuration & Data Files.

My settings/results disappeared after an update

They shouldn't — user data lives in a per-user directory (%APPDATA%\NetworkScanner / ~/.config/NetworkScanner), separate from the app folder that updates replace. See Configuration & Data Files for the exact locations.