Who's On Your Network? A Practical Checklist for Identifying Devices (Including That Kyocera You Forgot About)

Look, I'm not here to sell you on network monitoring software. I'm here to help you find out what's actually connected to your office network. Because as someone who's been in the trenches of business IT for the better part of a decade, I can tell you this: you almost certainly have devices on your network right now that you've forgotten about. And some of them might be a problem.

Let me be specific. I once spent a frantic afternoon trying to figure out why a client's network kept dropping. The culprit? A Kyocera DuraForce Pro 2 that someone had plugged into a charging cable on the network—and forgotten about. It wasn't malicious. Just... there. Sucking bandwidth. This kind of thing happens all the time.

So here's a checklist for you. It's not a theoretical guide—it's what I actually do when I walk into a business and need to understand their device landscape. I've broken it down into steps that you can follow right now. If you're dealing with a network slowdown, a security audit, or just that nagging feeling that something's off, this is for you.

One note before we start: I'll focus on the practical, not the perfect. This won't replace a professional network audit. But it will get you 80% of the way there in under an hour. If your situation is a medical device network or a production line with strict uptime requirements, call a specialist. This checklist is for the rest of us.

Step 1: Start With Your Router or DHCP Server

Your router is the gatekeeper. It assigns IP addresses via DHCP—find the client list. This is where you'll get a raw snapshot of what's currently visible. The exact menu name varies (Connected Devices, DHCP Client List, Attached Devices), but it's always there. Log in, find it, take a screenshot.

What you're looking for: Device names, MAC addresses, IP addresses, and whether they're wired or wireless. Don't worry about the technical names yet. Just get a list. You'll see things like "android-4a3b" or "Tp-Link_Extender" or that Kyocera printer nobody remembers installing.

In my experience, most businesses have 2-3 devices they can't identify on first pass. That's normal. We'll fix that in a moment.

Step 2: Figure Out What Each Device Actually Is

Now that you have a list, you need to identify the unknowns. Don't guess. Here's a practical method I've refined over about 200 such lookups:

• Check the MAC address vendor. The first 6 characters of a MAC address are the OUI (Organizationally Unique Identifier). Type it into a tool like Wireshark's OUI lookup or just Google it. You'll often find that "00:1A:2B" is a Kyocera device or "00:14:22" is a Dell. This alone will identify 70% of unknowns.
• Ping the device. If it responds, note the response time. Fast (<1ms) usually means local. Slow suggests a bad connection.
• Check the hostname. Some devices broadcast a name. "DuraForce-Charging-Station" is pretty clear. "Workgroup-23" is not.
• Physically trace it. If you have access, unplug what you think is the device and see if it disappears from the list. I had to do this for a network once—turned out a Kyocera switchback connector was acting as a bridge for a second router I didn't know about. That took an hour.

After 5 years of doing this, I've come to believe that identification is 90% pattern recognition, 10% luck. It took me about 150 attempts to really get fast at it.

Step 3: Audit Your Physical Cable Infrastructure

WiFi gets all the attention, but the connectors and cables are where the real surprises live. Walk the office. Check every wall jack, every network closet, every desk. I'm serious.

Here's what I typically find:

• Disconnected cables still plugged into the switch. They're not active, but they clutter your network map.
• Daisy-chained switches. Someone needed more ports and just plugged a consumer switch into the wall. This creates loops, drops, and bizarre issues.
• Forgotten routers. I found one once in a break room, plugged into a Kyocera printer's network port—because someone wanted WiFi for their phone. It was creating a DHCP conflict that took us two days to track down.

The one thing most people miss: Check under desks and behind furniture. Those Kyocera printers with network ports? They make fantastic secondary access points if someone plugs a router into them. I've seen it three times.

Step 4: Check for Rogue Devices and Unusual Patterns

Now you have a list of identified devices and a clean cable map. The next step is checking for things that shouldn't be there.

Red flags:

• Unknown devices with vendor OUIs you don't recognize. A device from a brand you've never bought from? Investigate.
• Multiple devices with the same IP. Yes, this happens.
• Devices with random-looking names like "ESP_123ABC." These are often IoT devices, but could be anything.
• A sudden spike in connected devices. If you usually have 25 and now you have 35, something changed.

In March 2024, I had a client call with a network that kept maxing out at 20 Mbps. I assumed it was the ISP. I didn't fully understand the value of a device audit until I checked their connected list and found a Kyocera DuraForce Pro 2 that was running a tethering app. It was using the office WiFi as a backup for its cellular connection—and saturating the bandwidth. I still kick myself for not checking that first. A 10-minute audit would have saved us a full afternoon of troubleshooting.

Step 5: Document What You Found (And Set a Reminder)

This is the step most people skip. Don't.

Create a simple inventory spreadsheet: device name, type, MAC address, IP, location, and date added. Keep it in a shared drive or a group chat. This doesn't need to be fancy. It just needs to exist.

Set a calendar reminder to do this audit again in three months. Not six. Three. Networks change fast. New printers arrive. People plug in personal devices. The third time I had to re-trace a cable run for a client who'd moved desks, I finally set up a quarterly audit. Should have done it after the first time.

If you're thinking "I'll just remember," you won't. I've made that mistake. The amount of time I've spent re-discovering the same issues is embarrassing.

Honest Limitations: When This Checklist Won't Work

I recommend this checklist for businesses with under 50 devices and a straightforward network setup (one router, one switch, standard WiFi). But if you're dealing with any of the following, you'll need a deeper approach:

• Multiple VLANs or segmented networks. This method only sees the subnet your device is on. You'll need a network scanner or professional tools.
• Managed switches with port security. The DHCP list might not include wired devices if the switch is blocking broadcast traffic. Check the switch's ARP table instead.
• Industrial or manufacturing networks. Different protocols (Profinet, EtherCAT) don't show up on a standard DHCP list. Call a specialist.
• Guest WiFi networks. Those devices are isolated. You won't see them from your admin interface unless you log into the guest network separately.

For 80% of small to medium businesses, this method works just fine. Here's how to know if you're in the other 20%: if your network has more than three switches, or if you have a dedicated IT person, you probably need more. But if you're the office manager who also handles IT, or the small business owner doing it all, start here. It's better than a perfect plan you never execute.

Prices as of 2025: verify current rates for your specific hardware. Network switches cost anywhere from $50 (consumer) to $5000 (enterprise). Your mileage will vary. But the time you spend on this audit? That's free. And it might save you a headache later.