Okay, this hardware problem has been bugging me for almost 2 months now, and I can’t stand it any longer. Ever since I installed a new router (the D-Link DIR-655), I have run into a rather perplexing problem: My laser printer will not wake from sleep when I send a new print job through. I have to power cycle the printer in order for it to print.
I have a Brother 2070N laser printer that’s connected to my D-Link router via a CAT-5 Ethernet cable. The problem started with the D-Link router – my previous Cisco router (the one that died) never had this issue. I’ve waded through the documentation, looked through the Brother web-based printer admin panel, thrown salt over my shoulders, rubbed a dead turkey and even attempted ritualistic voodoo, but nothing I do seems to get my printer to wake from its hibernation to print.
So I’m asking my fellow geeks and IT specialists for help. How do I get my Brother 2070N laser printer to wake from sleep on its own?
Thanks!
-Krishna
12-29-10 Update: I finally have things working now. The solution was more of a work-around than anything else, but at least it works. I bypassed the D-Link router / Ethernet port completely and connected the Brother printer to my PowerMacG5 via USB. From there, I installed the Brother drivers for Leopard, and made sure “Sharing” was turned on in the Printer & Faxes systems preference. The printer’s now shared via Bonjour, and all the Macs in the house now see the printer at all times. Crisis averted!
I may be off target here but it sounds like the issue you are having is that the WON (Wake On Lan) request is not being sent via the D-Link, which from many forums sounds like a common problem on their models. Not having the same devices at my site I’m unable to test them accurately, but the following link is to a forum that discusses the WOL issues with the DIR-655. Hope it helps:
http://forums.dlink.com/index.php?action=printpage;topic=5934.0
I don’t think it’s a WOL issue. Try setting the printer network connection to 100mb Full Duplex from the management web interface in case it’s an auto negotiation issue.