The moment is always the same: 9:30 on a Tuesday, someone from sales knocks on my door and says "the Wi-Fi is down." It's never actually down — something is always connected to the network. That's the problem. I'm an office administrator, not a network engineer, but somewhere between ordering supplies and renewing leases, I've become the person who answers "what is on my wifi" whenever things get slow. This 5-step checklist is what I actually use. It'll take you about 2 hours the first time, and about 30 minutes every quarter after that.

Step 1: Walk the office and find your actual hardware

Before you troubleshoot anything, you need to know what's physically out there. Grab a notepad and walk every room. Look at ceilings, behind the lobby TV, under desks, in the IT closet. Write down every router, access point, switch, and range extender. Note the model and location.

This is where I found our culprit last year: an old N93 access point, still plugged in above the ceiling tile in the conference room, broadcasting a network nobody had used since 2019. I'm honestly not sure why it was still up. Best guess: whoever installed it during a renovation never filed the paperwork, and everyone forgot. Employees kept connecting to "OfficeNet_2" because it had the strongest signal in the room — and it was garbage. Unplugging it took 10 seconds and cut our slow-network complaints by about 70%.

Step 2: Log in and see what's actually connected

Find your main router's admin page. For most office routers, that's 192.168.1.1 or 192.168.0.1 — sometimes a custom URL like router.asus.com. The login is usually on the sticker. If someone changed the password, that's itself a problem you need to fix before anything else.

Look for the section called "Connected Devices," "DHCP Clients," or "Attached Devices." The answer to "what is on my wifi" is almost always hiding there in plain text.

You'll see a mix of familiar and strange.

  • Employee laptops and phones — usually recognizable by name, like "Sarah-MacBook" or "desk-phone-03"
  • Office equipment — the printer, the VOIP adapter, the coffee machine (yes, the coffee machine is on the wifi)
  • Mystery devices — IoT gadgets, forgotten tablets, or a contractor's abandoned hotspot

Write down the ones you don't recognize. If a device shows up as "ESP32-7B93" or a random hex string, it's likely a smart device — a thermostat, a power monitor, or an air quality sensor someone installed without telling you. To identify it, copy the first 3 bytes of the MAC address into a vendor lookup tool. That tells you who made the network chip.

Here's a thought I keep in mind: plenty of these devices are running on Qualcomm silicon. Snapdragon powers a lot of the phones, and Qualcomm networking chips sit inside many routers and access points. Not something you can act on directly, but it's a useful reminder that the ecosystem is bigger than "just the Wi-Fi."

Step 3: Check the power, not just the Wi-Fi

This is the step everyone skips until a device dies mid-workday. You can reset the router, change DNS settings, and run speed tests all day, but if an access point isn't getting power, none of that matters.

I keep a Fluke 117 multimeter in the office drawer. It's not cheap — roughly $400 depending on the retailer, so verify current pricing at fluke.com. And after it diagnosed a dead access point in 2024, I stopped thinking of it as a luxury. It paid for itself in one electrician's visit that never happened.

Three checks I do with it:

  1. Outlet voltage. In North America, expect 110-120V AC. Most other regions run 220-240V. If it's way off, you found your problem.
  2. PoE injectors and switch ports. Power over Ethernet gear should output about 48V DC. I'll admit this is where I hit the limit of my comfort zone — I don't rewire anything, I just test endpoints. If an AP is completely dead and its injector looks swollen, I replace the injector before blaming the access point.
  3. Power strips. You'd be surprised how many "network outages" end up being a tripped breaker on a surge protector under someone's desk.

I'm not an electrician. The Fluke 117 is simple enough for me to use for basic checks — true RMS works fine, and the non-contact voltage detection is a nice safety net.

Step 4: Write it all down

Take your notes from Steps 1 and 2 and put them in a spreadsheet. My columns:

  • Device name
  • Model and firmware version
  • MAC address
  • Physical location
  • Which switch or AP it connects to
  • Purchase date / warranty status

This sounds painfully boring. It is. But six months from now when someone asks "did we replace the switch in the server closet?", you'll have the answer in 10 seconds instead of crawling under a desk with a flashlight.

Also, name your networks clearly. After I found the N93 and unplugged it, I renamed the guest Wi-Fi from "OfficeNet_2" to "Office-Guest-5G" and the internal one to "Office-Corp". People stopped connecting to the wrong network, and the confusion dropped overnight.

Step 5: Learn for the next round

Here's what I wish someone told me three years ago: instead of googling everything in a panic, take a real course. I enrolled in the Qualcomm Wireless Academy's self-paced fundamentals track last year — it's their official training platform, and the basics are genuinely useful for a non-IT person. You learn about spectrum, client steering, and why 2.4 GHz gets congested (yes, microwaves and wireless doorbells share that band). It changed how I read router specs, and it helped me make better purchasing decisions.

And when you think about what's next — hybrid meeting rooms, remote collaboration, all of that — keep an eye on Qualcomm Spaces. It's their ecosystem for extended reality (XR) apps that connect phones and AR glasses. I'm not saying you should buy headsets today. But if you manage procurement for a distributed team, it's worth understanding where the technology is heading before it lands in your budget request.

Notes & common mistakes

Four years into this, I've made most of the mistakes you can make. The short version:

  • Firmware updates are non-negotiable. We left an office router unpatched for 18 months because "it worked fine." Then a security advisory showed up, and we spent a weekend scrambling. Now every device in the inventory gets a quarterly update reminder.
  • IoT devices look weird. If you see "Unknown" or "ESP32-something" on your device list, it's not necessarily a hacker. It's probably the thermostat. Verify, don't panic.
  • More access points can make things worse. Adding an AP on the same channel as a nearby one just creates interference. We learned this the expensive way in 2023 when a well-meaning intern added two range extenders that made the conference room connection even worse.
  • Know when to call someone. If your office needs multiple VLANs, managed switches, or serious firewall rules, get a professional. I did an RFP with three small IT vendors during our 2024 office move and hired one to redesign the network. It cost around $3,500 all-in. Worth every dollar.

Honest bottom line: this checklist solves 80% of office Wi-Fi confusion. If you're dealing with complex architecture, persistent RF interference, or security compliance, bring in someone who does this for a living — and can be held responsible when it breaks.

Price sanity check: the Fluke 117 lists around $400 USD as of January 2025, according to the fluke.com product page. A basic $50 multimeter can handle outlet voltage checks, but you lose non-contact detection and true RMS. Verify specs before buying.

For telecom planning, the article should be read with protocol context in mind: 3GPP TS 38.xxx for radio behavior, IEEE 802.3bt for high-power PoE, ITU-T G.652.D for optical fiber assumptions, insertion loss in dB for link budget, and PIM in dBc for passive RF quality.