Download LanScan for Mac

In the edit

LanScan 8.2.17 runs on any Mac with macOS 11 or later — Intel or Apple Silicon, it doesn’t matter. That covers everything from an old Intel MacBook Air to the latest M3 Pro. No extra dependencies, no command-line fiddling.

Here’s a realistic job: you plug into a new office network and need to know what’s out there. Open LanScan, hit Scan, and it walks through the local subnet using ARP packets for IPv4 and standard discovery for IPv6. Within seconds you see every active device, its IP, MAC address, and up to four host names. If the network has an SMB domain, that shows up too. You can hide columns you don’t need, add a custom comment to a device (handy for labelling a printer or a server), and scan anything from a small range up to the full IPv4 address space. No artificial cap on how many devices it finds.

Good for:
- IT folks checking what’s connected to a local network
- Photographers or videographers finding a NAS or a remote drive on location
- Anyone managing a small office network who wants a quick device inventory

Keep in mind:
- The public subnet scan uses Ping, SMB, and mDNS — it’s slower than a local ARP scan
- IPv6 scanning is supported but depends on your network configuration
- Interface is in English only

How LanScan fits with other tools and macOS

LanScan doesn’t replace a full network utility like WireShark or a terminal-based nmap — it sits a layer above them. For a wedding photographer working on location, that’s exactly the right place. You open LanScan to find the NAS you know is on the network but can’t see in Finder, get the IP address, and then mount it through the Connect to Server dialog. That’s the whole loop: scan, note, connect.

It also works well alongside a good network monitoring tool. Run LanScan once to map the network, save the CSV export, then hand that list to something like PingPlotter or a custom script if you need ongoing health checks. For the one‑off inventory job, LanScan does the heavy lifting and the CSV file gives you clean data to drop into Numbers or Excel.

On the macOS side, LanScan picks up whatever interfaces are active — AirPort, Ethernet, Thunderbolt Bridge, even virtual interfaces from Docker or Parallels. That means you don’t have to tell it which network to look at; it just finds the right one. If you’re switching between Wi‑Fi and a wired connection in a co‑working space, the scan adapts automatically. The column‑hiding and alignment options help you see only what matters for the current job, which is a small but welcome touch when you’re in a hurry.

Hide host name and comment to speed up scanning

Before you run your first real scan, a couple of small tweaks save time. Open the preferences and look at the columns. By default, LanScan shows everything, but if you only need IP and vendor, hide host name and comment until you need them. That keeps the list compact and scannable.

If you regularly scan the same subnet, set a custom IP range instead of scanning the whole subnet every time. A full IPv4 scan on a busy network can take a while, especially over Wi‑Fi. Narrowing the range to, say, the DHCP pool (often 192.168.1.100 to 192.168.1.200) gives you a result in seconds rather than minutes.

The comment field is easy to overlook. Once you identify a device — “Printer Room B” or “Synology NAS” — type a comment and it stays saved for the next scan. After a few uses, the list becomes your own annotated network map.

Don't expect public subnet scans to run as fast as local ones

The most common one is expecting a public subnet scan to be as fast as a local one. ARP‑based local scanning is near‑instant because it talks directly to the network hardware. The moment you scan a public range or a subnet outside your local broadcast domain, LanScan switches to Ping, SMB, and mDNS. That’s slower, and it depends on the remote devices responding. Beginners often think the scan is stuck when it’s just waiting for timeouts.

Another mistake is ignoring the interface selection. LanScan auto‑detects active interfaces, but if you’re connected to two networks at once (say, a corporate Ethernet and a personal Wi‑Fi hotspot), it may scan the wrong one. A quick glance at the interface name in the toolbar confirms you’re on the right network.

Finally, people sometimes forget that LanScan shows only devices that respond to discovery packets. A device with a strict firewall or a misconfigured network stack might not appear even if it’s physically connected. That’s not a bug — it’s the nature of passive network scanning. If something important is missing, check that the device is awake and on the same VLAN. A quick ping from Terminal can confirm before you blame the scan.

Mac it needs

• macOS 11 or later
• Apple Silicon or Intel processor