D
Doug Ratcliffe
My client broke the paper tray on printer#1 so everyone
sent jobs to printer#2. It ran out of paper. Jobs backed up
on the server & even after reloading the paper, the printer
status on the server was "out of paper". Oddly enough the
exact same problem occurred 4 hours later in my own office
on my own network. I sent 3 jobs directly over the network
to a printer that had run out of paper. Two jobs printed
out after reloading paper. The 3rd job was still in the que
and the printer status still showed as "out of paper". I
decided not to do anything except ping the ip address,
think, have a coffee & a smoke. When I returned 10 minutes
later, the printer status was "ready" and my print job had
completed. It was the same small Excel file, lazy me, I
just clicked the printer icon 3 times for 3 copies. The
ONLY THING that I can think of is that installing SP3 for
Office XP last week is somehow affecting TCP/IP printing.
sent jobs to printer#2. It ran out of paper. Jobs backed up
on the server & even after reloading the paper, the printer
status on the server was "out of paper". Oddly enough the
exact same problem occurred 4 hours later in my own office
on my own network. I sent 3 jobs directly over the network
to a printer that had run out of paper. Two jobs printed
out after reloading paper. The 3rd job was still in the que
and the printer status still showed as "out of paper". I
decided not to do anything except ping the ip address,
think, have a coffee & a smoke. When I returned 10 minutes
later, the printer status was "ready" and my print job had
completed. It was the same small Excel file, lazy me, I
just clicked the printer icon 3 times for 3 copies. The
ONLY THING that I can think of is that installing SP3 for
Office XP last week is somehow affecting TCP/IP printing.