When a client first called us, they were ready to switch internet providers.
“We’ve upgraded our plan twice. We’re paying for speed we never seem to get,” they told us.
The real issue wasn’t the internet. It was something much closer to home—and far less obvious.
Over the course of a two-week network audit, we discovered that one device—just one—was responsible for nearly 4 out of every 10 support issues they’d experienced in the last six months.
And no one had caught it.
Here’s what it was, how we found it, and how we made sure it never caused problems again.
The Symptoms: Unreliable and Inconsistent
The client, a professional services firm with around 40 employees, had been struggling with issues that seemed random:
- Zoom calls would freeze or drop out
- Uploads to cloud storage stalled for no clear reason
- Certain staff members complained that their internet worked “fine one day and awful the next”
- One entire section of the office had spotty Wi-Fi, even with extenders in place
They’d worked with another provider who told them to reboot their modem and consider “higher-speed internet.” But they’d already done that—twice.
We stepped in with a full diagnostic review as part of our managed IT services approach.
The Investigation: Digging Deeper Than Surface-Level Monitoring
We started with what we always do for new clients: a combination of endpoint logs, firewall traffic monitoring, and user-reported ticket analysis.
Within a few days, we saw a strange pattern—one MAC address generating constant bursts of activity. It was subtle, but consistent.
The source?
A 6-year-old network printer sitting in the copy room.
It was broadcasting nonstop mDNS traffic (multicast DNS), flooding the network with unnecessary discovery packets. Even worse, its IP settings were misconfigured and intermittently collided with a critical internal file server.
It wasn’t just slowing things down. It was creating network instability.
The Fix: Structured, Not Just “Quick”
We didn’t just disable the printer or slap a Band-Aid on it. This is part of what sets our managed IT support apart—it’s structured, not reactive. We approached it like we would for a larger environment:
- Reassigned all printers to a dedicated VLAN, isolating traffic
- Turned off unneeded protocols (mDNS, NetBIOS, WSD)
- Set proper static IPs with DHCP reservations
- Documented every step so future devices don’t repeat the mistake
- Ran a 30-day follow-up report comparing ticket volume and latency
Here’s what changed:
- 37% reduction in support tickets
- Faster uploads to cloud apps
- Zero dropped video calls reported since the fix
- No new hardware purchases required
The printer still works. But now, it’s behaving.
The Bigger Lesson: It’s Not Always What You Think
This isn’t just a “printer horror story.” It’s a reminder that most IT problems aren’t solved with one-click tools or guesswork.
We see this pattern a lot:
- An old device quietly hogs bandwidth
- A smart TV or camera creates chatter that nobody notices
- A poor IP structure causes random dropouts that mimic internet issues
Most providers don’t check for these things because they’re not easy to spot without the right tools—or they’re just too focused on reactive fixes.
Why Sirius Always Audits First
Every new Sirius client goes through a complete network health check. We look at the usual suspects, yes—but also the forgotten ones.
Because no one should be paying for high-speed internet just to have a printer eat up all the air in the room.
Still dealing with “mystery” slowdowns or outages?
Let’s run a quick audit. You might be surprised what we find.
