We have a customer in Teaneck NJ recovering from Sandy. The good news
is that the power is now restored and their location is fine. Server is
back up and all is good except one important network printer. When on
and all connected, it is spasmodically printing pages of gibberish. We
powered
Is it possible the driver got corrupted? I had that issue after a
breaker tripped on the USB printer attached to my desktop. I reinstalled
the driver, restarted CUPS all was well after that.
Jim Peterson
On Mon, 2012-11-05 at 10:16 -0600, Howard White wrote:
We have a customer in Teaneck NJ
had similar issue with workstation sending bad jobs to the printer (not
using queue on server)
On Mon, Nov 5, 2012 at 10:34 AM, Jim Peterson jim.sokytec...@gmail.comwrote:
Is it possible the driver got corrupted? I had that issue after a
breaker tripped on the USB printer attached to my
On 11/05/2012 10:57 AM, ware wrote:
had similar issue with workstation sending bad jobs to the printer (not
using queue on server)
Great observation. We just booted the customer server. While server
down, we restarted the printer and the nonsense printing resumed, all
the while the
I wonder if the network print server on the printer (HP JetDirect, in the
HP parlance) has gone bad? We've had a few of those go bad in the past.
Chris
On Mon, Nov 5, 2012 at 11:26 AM, Howard White hwh...@vcch.com wrote:
On 11/05/2012 10:57 AM, ware wrote:
had similar issue with
Hello Howard,
Is there any chance of configuring a box as a firewall to the printer so
you could see if there is any traffic to the printer and exactly where
it is originating? No firewall rules need to be there, but it would
make it possible to see what the traffic looks like and find out a bit
Another option might be to hook up the network printer to an old school
network *hub* and then hook up another computer, running Wireshark to sniff
the packets.
Chris
Chris
On Mon, Nov 5, 2012 at 6:45 PM, David R. Wilson da...@wwns.com wrote:
Hello Howard,
Is there any chance of
