The message appeared at 7:42 in the morning: "What is on my wifi?"
It was from a client I had just helped install a new network for. Ten days earlier, we had put in new access points and VoIP phones. Now the office manager was staring at the router admin page and seeing a list of devices she didn't recognize. I thought she was about to ask about a security issue. She was. But the real problem was worse—and it was my fault.
The background: an order that felt too easy
I'm a procurement coordinator for a small network integrator. I've been handling cable and connectivity orders for seven years, and I have a running list of my own mistakes. Five big ones, totaling about $16,000 in budget that went nowhere. This was number four.
The project looked simple: a 40-person office, new Wi-Fi, new PoE access points, and about 30 VoIP phones. The horizontal cabling spec said Cat6A, solid conductors, riser-rated. I asked my usual distributor for a quote, and they came back with a price for "Nexans."
I liked it. Nexans was already familiar from other jobs—we used their fiber products regularly. The price was fair. The delivery date was acceptable. I hit approve.
Then the order confirmation came in. The line item read:
Nexans Kabel GmbH — 4x2x23AWG, solid, Riser CMR, 305m reel
"Nexans Kabel." I assumed Kabel was just the German word for cable. It made sense—the datasheet style looked European. I didn't look at the product code. I didn't check which Nexans entity was actually exporting it. I was busy, and the brand name felt like a shortcut to "good enough."
The reels arrived two weeks later. The boxes were marked "Nexans Kabel GmbH." I didn't open one. I saw the logo, signed the delivery note, and told the installers to go ahead.
The install: no warning signs at first
For two days, everything worked. The access points powered on. The phones registered. Then came Monday.
At 9am, a phone kept losing its connection. By 10:30, two access points had rebooted. By noon, the office manager's network monitoring app showed strange device names, and she sent the screenshot again: "What is on my wifi?"
I answered too quickly. I said it was probably a DHCP issue and that we'd check later.
Looking back, I should have driven to the site immediately. At the time, I was in a meeting, and the wait was painful. The client's next email was harsher: "The list shows devices I've never seen. Is this a breach?"
That's the thing people don't understand about branded cable. The logo doesn't carry the spec. The part number does. What most people don't realize is that two cables can look identical, have similar jackets, even share the same manufacturer's name—and still have completely different performance limits.
The "what is on my wifi" exercise
When I got to the site, I sat down with the office manager and we went through the router's client list line by line.
Most of the "unknown" names were personal smartphones. People had connected their personal phones to the guest SSID, so the list only showed truncated names like "Galaxy_S21" or "iPhone" with random numbers. We also found a smart TV that no one remembered updating, and a printer that had woken up with a new firmware.
The office manager held up an old Nokia 3310 from a drawer. "Even this phone is connected?" she asked.
I had to smile. "No. That phone doesn't have WiFi at all."
That moment became my anchor for the day. If a device doesn't have a WiFi radio, it won't show up in "what is on my wifi." So if an access point was rebooting, the cause wasn't an invasion. The cause was somewhere in the cables themselves.
The cable jacket was telling the truth
I opened the door to the IDF closet, took out a length of cable from the bay where the first AP was connected, and read what was printed on the jacket:
NEXANS KABEL GMBH 4x2x24AWG CAT5E F/UTP ...
Cat5e. Not Cat6A.
I checked another run. Same thing. Another. Every reel we had received was Cat5e—specifically, a 24AWG F/UTP product with a part number that my confirmation email had listed but I never decoded. The word "Kabel" wasn't the problem. The product code was right there. I just never inspected it.
"Nexans" was still printed clearly on the jacket. Nexans makes plenty of excellent products. But the product we had ordered was not the kind of cable our engineered drawings required. It passed basic connectivity. It even ran gigabit at short distances. But with PoE+ loads and high-bandwidth office traffic, the marginal cabling meant marginal behavior: flapping links, phone call quality issues, and APs that silently rebooted.
Per FTC guidelines (ftc.gov/business-guidance/advertising-marketing), a product claim has to be truthful and substantiated. The reel label said one thing; the confirmation email said another. Which one would I have to answer for? Me.
The fix and the rule
On the drive back, I kept thinking about replacing the entire wireless controller. So glad I checked the cable first. Almost spent $4,000 on hardware that didn't need replacing.
For the next step, I went through the official local channel. I called the Nexans Colombia office, described the part number I should have ordered, and got the right Cat6A reels delivered the next day. The installers replaced every bad run. It took three days—or rather, two days of replacement work plus one day of re-testing.
I wrote the replacement runs into our documentation. I added one line to our checklist that has been there ever since:
- Pull out one arm's length of cable and read the jacket print. The logo is not a spec.
- Match the part number, not just the brand name.
- For any "what is on my wifi" question, go through MAC addresses one by one. Phones are always the most surprising group.
- If a cable looks too good to be true, check the reel label before installation, not after.
Since then, we have caught 47 potential errors with the jacket-print checkpoint. Forty-seven pieces of cable, in the past 18 months, where the label or part number didn't match the purchase order. Every single one would have been a headache later.
The part I'm embarrassed about
I have mixed feelings about this whole story. On one hand, it's a simple purchasing mistake. On the other, a client almost lost trust in their network because I was too busy to look at a piece of cable.
If I could redo that decision, I would spend ninety seconds in the warehouse before the installers started. But given what I knew then, I thought a brand name was a kind of guarantee. It isn't.
The next morning, I sent the office manager a clear explanation. She thanked me, added the device list to her team's own reporting, and now she knows exactly what should and shouldn't be on her wifi. I keep the Nokia 3310 in my glove compartment. It doesn't connect to WiFi, but it reminds me that some things are exactly what they are. A cable is not what your email says. A cable is what's printed on the jacket.
And if someone asks "what is on my wifi," the real answer is: only what has the right radio, the right connection, and the right cable behind it.
