How to see which devices are connected to your office network
For office admins who need a quick, reliable list of devices currently on the network. This guide shows the easiest dashboard-first way to find connected devices, plus a command-line fallback, and how to verify what belongs there and what does not.
TL;DR — To check which devices are connected to your office network, start in your router, firewall, or Wi-Fi controller dashboard and open the client/device list. The most useful next step is to compare that list against known company devices and flag anything with an unknown name, manufacturer, or IP address. Reading time: ~5 min
Goal
When you finish, you will have a current list of devices connected to your office network, including their names, IP addresses (the local network address), MAC addresses (the hardware network ID), and connection type where available, so you can spot unknown or unauthorized devices.
Prerequisites
- Admin login for your network equipment dashboard: your router, firewall, or Wi-Fi controller
- Permission to view connected clients/devices in that dashboard
- A computer or phone connected to the office network
- Your network gateway address if you do not know the dashboard URL yet; common values are
192.168.1.1,192.168.0.1, or10.0.0.1 - Optional: a terminal app if you need the command-line fallback
- Optional: a short list of known company devices to compare against: laptops, printers, phones, cameras, TVs, meeting room gear
Steps
Step 1: Open your network device dashboard
Use one of these exact addresses in your browser, one at a time, until a login page appears:
http://192.168.1.1
http://192.168.0.1
http://10.0.0.1
If your office uses a managed firewall or Wi-Fi system, open your provider's dashboard instead. In most dashboards, the path you need is one of these:
Dashboard → Clients
Dashboard → Connected Devices
Dashboard → Device List
Dashboard → Network → Clients
Dashboard → Status → LAN → DHCP Clients
Dashboard → Wi-Fi → Stations / Clients
What you should see: a login page, then a page listing devices with columns such as Name, IP, MAC, Status, or Connection Type.
Step 2: Find the live client list
After you sign in, open the client/device list. If there is a filter, set it to the literal values below where available:
Status = Online
Time range = Now / Current
Network = All networks
Connection = Wired and Wireless
If your dashboard separates wired and Wi-Fi devices, open both of these paths:
Dashboard → LAN → Clients
Dashboard → Wi-Fi → Clients
What you should see: a list of devices that are currently connected, not just historical devices seen in the past.
Step 3: Record the key details for each device
Create a simple checklist in a spreadsheet or note and copy these exact fields from the dashboard for each device shown:
Device Name
IP Address
MAC Address
Connection Type
Manufacturer / Vendor
Last Seen
Network / VLAN
If your dashboard has an export button, use it. Common labels are:
Export
Download CSV
Export client list
What you should see: a saved list you can review without clicking into each device again.
Step 4: Identify your own computer in the list
This helps confirm you are looking at the right network and gives you a known-good example.
On Windows, open Command Prompt and run:
ipconfig
On macOS, open Terminal and run:
ipconfig getifaddr en0
If that returns nothing on macOS, run:
ipconfig getifaddr en1
On Linux, run:
hostname -I
Now match that IP address to the same IP in the dashboard's client list.
What you should see: one device entry with the same local IP as your computer.
Step 5: Flag unknown or risky devices
Review the list and mark anything that matches one or more of these literal conditions:
Name is blank or generic, such as "android", "esp", "unknown", or "localhost"
Manufacturer is unfamiliar
Connection Type is Wi-Fi when the device should be wired
Last Seen is current, but nobody recognizes the device
Network / VLAN is the office LAN instead of guest Wi-Fi
There are multiple devices with nearly identical names you did not expect
If your dashboard supports device details, open the device and check these paths where available:
Clients → [device] → Details
Clients → [device] → Traffic
Clients → [device] → Port / Access Point
What you should see: a short list of devices that need confirmation from your team.
⚠️ Do not click "Block", "Quarantine", "Forget", or "Remove lease" yet unless you are certain the device is not needed. Blocking the wrong device can disconnect printers, phones, cameras, or meeting room systems during business hours.
Step 6: Use a command-line fallback if the dashboard is incomplete
If the dashboard is unavailable or only shows partial information, scan from a computer on the office network.
If nmap is installed, run:
nmap -sn 192.168.1.0/24
If your network uses 192.168.0.x, run:
nmap -sn 192.168.0.0/24
If your network uses 10.0.0.x, run:
nmap -sn 10.0.0.0/24
Then show your computer's ARP cache (the local table of recently seen devices):
On Windows:
arp -a
On macOS or Linux:
arp -a
What you should see: a list of active IP addresses and MAC addresses you can compare with the dashboard.
Step 7: Separate office devices from guest devices
From a security and segmentation angle, confirm that non-company devices are not on the main office network.
In your dashboard, check these exact areas where available:
Dashboard → Networks
Dashboard → VLANs
Dashboard → SSIDs / Wi-Fi Networks
Dashboard → Guest Network
Look for client entries attached to these literal network types:
Office LAN
Corporate
Staff
Guest
IoT
Voice
Cameras
What you should see: employee laptops and business systems on the office/staff network, and visitor phones or personal devices on Guest or another separate network.
Verify it works
Use both a dashboard check and one local check.
- In the dashboard, refresh the client list:
Clients → Refresh
Connected Devices → Reload
Expected result: your current computer or phone appears as Online with a current "Last Seen" time.
- Confirm your device's local IP matches the dashboard entry:
Windows:
ipconfig
macOS:
ipconfig getifaddr en0
Linux:
hostname -I
Expected result: the IP shown on your device matches one device in the dashboard.
- If you used
nmap, confirm at least one known device appears in both places:
nmap -sn 192.168.1.0/24
Expected result: a known printer, laptop, or your own computer appears in the scan and in the dashboard list.
Common pitfalls
You opened the ISP modem page, not the main office router or firewall
Mistake: logging into the internet modem instead of the device that manages the office LAN and Wi-Fi.
Symptom: you only see internet status, or the device list is empty or very short.
Fix: open the dashboard for the router, firewall, or Wi-Fi controller that actually hands out local IP addresses, then go to Clients or Connected Devices.
You are looking at historical devices, not current ones
Mistake: using a page that shows every device ever seen.
Symptom: the list includes old phones, former employees' laptops, or devices marked offline from weeks ago.
Fix: set the filter to Status = Online or open the page labeled Current, Active, or Connected.
You only checked Wi-Fi clients
Mistake: reviewing wireless devices but not wired ones.
Symptom: printers, desk phones, cameras, or conference room hardware are missing.
Fix: open both LAN → Clients and Wi-Fi → Clients, or set Connection = Wired and Wireless.
Your scan used the wrong subnet
Mistake: running a scan against 192.168.1.0/24 when your office network is actually 192.168.0.0/24 or 10.0.0.0/24.
Symptom: nmap finds almost nothing.
Fix: check your own IP first with ipconfig or hostname -I, then scan the matching subnet.
You treated an unknown name as an unknown device
Mistake: assuming a generic hostname means the device is unauthorized.
Symptom: you nearly block a legitimate TV, printer, camera, or IoT device.
Fix: compare the MAC address and manufacturer in the dashboard before taking action, and confirm with your team if the device belongs to meeting rooms, security, or facilities.
Guest devices are mixed into the office network
Mistake: visitors joined the main staff Wi-Fi instead of Guest.
Symptom: many phones and tablets appear on the same network as company laptops and printers.
Fix: move visitor access to Guest and confirm the dashboard shows those devices under the guest network or guest VLAN.
This article was written by an AI system and published pending human review. Verify anything you intend to act on.
Have a project in mind?
Get an instant AI price estimate for it, or talk directly to our team.
One email a month on what we learn building with AI