Discover all network devices in your organization with these command-line and scanning tips to map a subnet with arp, transform results into a device inventory and network monitoring solution for Linux, Windows and macOS, and Proxmox-based devices. This answers the question how to list all network devices and find all connected devices and their connection types, including wi‑fi, router, IP addresses, and mac address.
On linux, including Ubuntu and Debian, list each network interface with command-line ip link show or ip addr to view ip addresses; predictable device name conventions (enp…, wlp…) have replaced eth0, but you can verify this with ls /sys/class/net. On macOS, networksetup -listallhardwareports maps hardware ports to the BSD device name convention, and scutil --nwi shows the active network interface connections; for wi-fi, ethernet, and mac address troubleshooting, consult ifconfig.
Windows CMD arp -a (after a broadcast ping to enumerate targets) lists connected devices on the local network; net view /all is a more limited host browsing command that only returns SMB hosts, and PowerShell Get-NetAdapter reports NIC details with -Physical or -IncludeHidden. On Proxmox, ip a will list interfaces, while /etc/network/interfaces holds the configuration for each on all these platforms; the total will vary per router, firewall and subnet mask applied across the subnet, and can also be segmented across multiple network segments or zones.
For context, see network devices before you plan to discover and monitor all devices as you scale.
Ping sweep the local network to start, and inspect the ARP table to enumerate connected devices by their IP addresses and mac address. Results may vary by router configuration, firewall settings, VLAN design, and wi‑fi coverage and wireless access point isolation, as well as the subnet mask in place. To see the devices on a network connected via wi‑fi, with practical patterns, see how to find IP addresses on your network.
If allowed, use nmap host discovery (nmap -sn) to broaden the network discovery scope across a subnet. This won’t work if ICMP is blocked. Workgroup or domain browsing with net view /all can list the SMB hosts, but misses many other network devices. Compare DNS records, DHCP leases and hostname fingerprints to identify unidentified nodes; see the great device detective: unmasking the network's hidden identities and review the leading network device monitoring tools for your selection criteria.
Direct answers: To list all devices on a local network, combine interface checks with arp or an approved nmap scan across network segments and locations. To check all computers on a network, run permitted host discovery (network-wide or segmented) on the subnet and confirm against DNS and DHCP data. To see all connections on a network, correlate with the routing context and perform basic network scanning for unlisted devices, then operationalize notifications, real-time trends, and network performance baselines in PRTG Network Monitor for ongoing visibility.
Turn these one-off checks into a schedule. Auto-discover across groups or devices with an auto-discovery workflow in PRTG Network Monitor, match network devices by IP addresses and hostname, and add sensors automatically across platforms, operating systems and network segments. Instead of spreadsheet upkeep, you get live inventory that tracks every network interface, nic and device name.
For selection context, survey the leading network device monitoring tools. Favor discovery that can span a subnet and local network, honors network security policies, and collects detailed information via SNMP, ICMP, and TCP but stays aligned with DHCP, DNS, router and modem settings, and wi‑fi and ethernet limitations.
Standardize coverage with device templates so every new device connected inherits the right checks. Close gaps with recommended sensors, and enter an IP range during setup so first-run discovery seeds these predefined sensors. This keeps topology and nodes current, while also aligning with firewall zones and subnet conventions.
Operationalize this visibility with notifications, real-time trends, and network performance baselines to catch latency spikes and network traffic anomalies before they impact users. As your inventory scales across macOS, linux, and Windows devices, keep names consistent, track mac address changes, and maintain network discovery that makes sense for your wireless network and modem limits.
Validate what’s visible on each local network, cross-check state on each network interface and device name, then extend network discovery to live nodes and map the gaps across network segments. Schedule recurring inventory updates with templates to add sensors, layer in notifications and baselines to improve network performance and downtime, and operationalize this end to end.
Align coverage to topology using ICMP and SNMP for more detailed information while also respecting the subnet mask and wi‑fi networks in use. When you’re ready to operationalize this end to end, get a demo.
Start with what you already collect: DHCP lease logs, switch MAC address tables, wireless controller client lists, and LLDP/CDP neighbors. Correlate hostname and device name, tag owners, and compare results across network segments to spot gaps.
See discover and monitor all devices
Account for MAC randomization, guest isolation and roaming. Pull client sessions from the wireless controller API, tie SSIDs to VLANs and wireless access point locations, and match corporate devices via MDM so identities persist over time.
Get practical tactics in the great device detective: unmasking the network's hidden identities
Time-box discovery to change windows, capture timestamps and data sources, and reconcile nodes to ownership and lifecycle status. Track drift monthly, validate against access control lists, and close decommissioned entries to keep the inventory clean.
Strengthen your process with network assessment.