It started with a dead printer and a bad Tuesday
In February 2024, our office printer died mid-job. Not in a slow, predictable way—it just stopped, right as our HR manager was printing 200 pages of benefits enrollment forms. She looked at me like I'd personally unplugged it.
I'm the office administrator for a 180-person company. I manage all the equipment and supply ordering—roughly $140,000 a year across eight vendors. I report to both operations and finance, which means when something breaks, I hear about it from two directions before lunch.
That Tuesday, I had two options: pay a repair tech to look at a six-year-old machine, or replace it. I chose replace. And that decision is where this story actually starts.
The purchase (and the quiet doubt)
I compared three options. A consumer-grade laser printer for around $300. A mid-range business unit for about $600. And the Lexmark MS810dn, which was closer to $1,200.
Honestly? I stared at that $1,200 number for a while. My finance lead had already asked me twice that quarter to "look for savings." The $300 printer would have made that conversation easier.
But here's what most buyers focus on—the sticker price—and completely miss: what happens when the machine acts up. The MS810dn had built-in diagnostic reporting, a support line that didn't route me to a chatbot, and a duty cycle rated for a small department, not a home office. I'd been burned before by cheap equipment that failed at the worst possible moment.
So I bought the Lexmark. And for about three weeks, it was great. Fast, quiet, no drama.
Then it connected but stopped printing.
The "connected but not printing" spiral
If you've ever seen a printer show up as online in the device list, accept a job, and then just… sit there, you know the feeling. The job disappears from the queue. The printer's display shows no errors. Nothing happens.
I did what anyone does. Restarted the printer. Restarted the computer. Deleted the driver and reinstalled it. Swapped the Ethernet cable. Unplugged the printer for 30 seconds, then a full minute, then (out of frustration) five minutes.
Nothing.
By day two, I'd pulled our IT contractor into it. He's a good guy—doesn't talk down to you, doesn't bill for every sneeze. We sat in the server closet, and he started looking at network traffic rather than the printer itself.
That's when things got interesting.
The network was a mess—and not just because of the printer
Here's something vendors won't tell you: the printer is usually the messenger, not the problem. Enterprise machines like the MS810dn log connection events aggressively. Ours had been dropping off the network for 10–15 seconds at a time, several times an hour. Not enough to notice during normal printing, but enough to kill a large print job the moment it started.
So we went looking for what was causing those drops.
What we found in the browser history and firewall logs was… a lot. One employee had spent part of a Tuesday afternoon researching how to use a betting calculator—on a work laptop, on our network, during business hours. Another had been poking around a blox fruits calculator, which I had to Google to understand (it's a gaming tool, apparently). And then there was the one that made our IT guy laugh out loud: someone in accounting had visited a female delusion calculator site. I still don't fully understand what it does, and I've chosen not to ask.
None of these sites individually took down our network. But collectively—along with a few streaming services and some unapproved browser extensions—they were pushing our aging router to its limit. The printer wasn't broken. The pipe was just too crowded.
What actually fixed it
Two things, in this order.
First, we replaced the office Wi-Fi router. It was five years old and had never been updated. That alone stopped the connection drops.
Second, I sent a company-wide email reminding people that work devices are for work—and that if they needed to research betting odds or game calculators, they should do it on their phones, on their own time, on their own data.
To be fair, I get why people do this. Nobody's perfect, and I've definitely checked personal email on the clock. But there's a difference between checking email and streaming video during a print job.
Once the router was replaced and the network traffic calmed down, the Lexmark printed flawlessly. It's still running now, eight months later, without a single jam.
The lesson I keep coming back to
I almost bought the $300 printer. If I had, here's what would have happened: the same connection drops, the same failed jobs—but I would have blamed the printer. I would have returned it, bought another cheap one, and repeated the cycle. The problem was never the machine. It was the infrastructure around it.
That's the thing about value versus price. The MS810dn cost four times more than the cheap option. But it also told me, in its logs, exactly what was going wrong. The cheap printer would have just sat there, silent, while I lost my mind.
In my opinion, the extra $900 bought me two things: a diagnostic trail that saved our IT contractor about six hours of guesswork (at roughly $150 an hour, that's $900 right there), and a reason to fix the actual root cause. A cheap printer would have just been replaced. Again. And again.
My experience is based on one office, one printer, and one very chaotic network. If you're running a smaller setup—five people, one room—your math will look different. But if you're managing equipment for a real team, do the boring thing: check your network before you blame the device.
And maybe glance at your firewall logs. You might find out more about your coworkers than you wanted to.
Discuss this writing program topic