Discover devices on your authorised network with Nmap

Validate the subnet first

A /24 example covers 256 IPv4 addresses, not just the three computers you expect to find. Confirm your real address, mask and approved scope before running a subnet command. Do not assume every home or office uses 192.168.1.0/24.

Use ip -brief address on Linux or Get-NetIPAddress on Windows to inspect the client, then compare with the router's network configuration.

Review scope without contacting target hosts

For an explicitly approved lab range:

nmap -sL -n 192.168.50.0/24

The list scan shows targets. With -n, it avoids reverse-DNS resolution. Read the count and addresses; correct the range before moving to active discovery.

Run host discovery only

nmap -sn -n 192.168.50.0/24

The -sn option skips the ordinary subsequent port scan. Discovery still sends network traffic. The exact probes depend on privileges, address family and whether the targets are on the local link. It is not simply equivalent to one ICMP ping per computer.

Build an inventory comparison

1. Record responding addresses and the scan time.
2. Compare them with your authorised device list and DHCP leases.
3. Investigate unknown entries through the router or device-management record.
4. Check expected but missing devices separately before declaring them offline.

A MAC vendor label, where available, can be a clue but is not a guaranteed device identity. Wireless privacy features, virtual adapters and relays complicate identification.

Verify a missing host

Check its power, current IP and network segment. A firewall may suppress discovery responses, and guest Wi-Fi may isolate clients. A remote routed scan can behave differently from a scan on the same LAN. Test the intended service on one known host rather than scanning ever larger ranges.

Common mistakes

Counting responses is not a complete asset inventory. DHCP changes can make an address refer to a different device later. A no-port-scan option still creates traffic and does not remove the need for authorisation. Avoid public internet ranges and fragile devices in this beginner exercise.

Document the result

Keep a dated map from device owner to address, with unresolved entries clearly marked. A useful inventory explains expected and unexpected devices rather than presenting an IP list as definitive proof of every computer on the network.