Workcentre 3335 reboots when going to sleep

[mcogs · Accepted solution]

I know it has been a while and no one had any workable solutions. I do have to say that Xfinity insisted that it was the printer/manufacturer problem even though nothing changed except me using their router.

Also, talking with various IT professionals, the common conclusion was the router was "polling" the devices and this somehow made the printer reboot when a WOL - wake on LAN was received. I had changed the IP scope in the router, thinking the printer didn't like the 10.10.x.x, but that did not fix it.

So, oddly enough, one evening of using the printer, they all started playing nice with each other. Finally.

I thank everyone for their comments or views.

Keeping fingers crossed.

[CathyO-Xerox]

Hello mcogs,

I see no one has responded to this post yet. So, at this point I would recommend contacting your local Xerox Support Department to speak with a Product Specialist for more assistance. Please call 1-800-821-2797 or 1-800-835-6100. 

[mcogs]

I've had my Workcentre 3335 for a few years now and it worked great printing from any computer in the house including iPhones. Recently I upgraded my internet to Xfinity's XB8 router (I had a TP-Link prior). Now the printer restarts when it goes into sleep mode. This happens only when the ethernet cable is plugged in OR it connects through WiFi. When I disable WiFi and unplug the ethernet, the goes into sleep mode fine. 

I have tried a static IP for ethernet and WiFi separately. I have tried only ethernet, only WiFi and both. I have noticed that with every restart, the "POPO" count goes up. I have tried to change the Power Saver Mode 1, 2 settings with no effect.

When it is connected to the network, it does print fine, like before, from any device.

If I connect the printer back into the older TP-Link router, does not restart when entering sleep. I do not know how the router could be effecing this. I understand a "wake on LAN", but not a Power off/Power on.

I have tried other electrical outlets/circuits and it still malfunctions. Other things I have tried: Factory network reset, upgrade firmware, reinstall driver, factory reset router, new ethernet cable, routing through a switch.