Ever since I hooked my printer up to the Ethernet (over a patch panel), it makes a ticking sound exactly every three seconds.
Before, it was connected via Ethernet cable to a Raspberry Pi that served as WiFi adapter, and that setup didn’t tick.
Update: The ticking stopped after deactivating DHCP. It’s a Kyocera Ecosys M5526cdn.
Have you opened it and checked for a bomb?
Could be a classic Bomb.
Support for classic bombs was dropped in the latest firmware update.
Gods damn… and what should I do now? I have an antique collection of bombs!
I work in IT support and would probably put a bomb in a printer. Can’t support it if it’s blown up
If it’s blown up you just have to install and configure a new one.
I’ve found the source of the ticking, it’s a pipe bomb!
Yaaaay!
Basic trouble shooting cause this is weird and I have no idea:
-
If you disconnect the Ethernet, does it still tick?
-
Does restarting the printer help?
-
Can you turn the printers wi-fi off?
My wildest guesses are it could be trying to print off a test page, receiving a signal to print but no info, or maybe it’s switching between checking WiFi and Ethernet.
I deactivated DHCP and gave it a fixed IP. The ticking stopped.
Could you share which brand and model it is, in case someone else runs into this issue?
Kyocera Ecosys M5526cdn
This is absolutely fascinating. I can’t even.
What in the actual fuck??
Fantastic, glad you figured it out. Thanks for updating us!
-
There isn’t really enough information here to diagnose what’s actually happening, but that sure is weird
maybe it’s waiting for you to tock?
It’s counting down the time until the enforcers arrive. They’ll rough you up for not buying enough ink. If you complain they’ll point to a clause in the EULA that you agreed to.
Bees in the cable got in the printer. Cable bees tick instead of buzz.
