We are using a Phaser 4510 networked printer in a computer lab with 30 Windows 7 workstations. The printer works great when the print jobs are sent one at a time, but when 20-30 jobs get sent within a 1 minuet period the printer will print 2 or 3 and then stop without any error.
If no action is taken, 1 or 2 print jobs will eventually come out over the next several hours. New print jobs sent after the printer has “stalled” do not come out either.
Power cycling the printer has no effect. However we can get the queued jobs to print by clearing the NVram.
The size of the print job seems to have no effect on the problem, a single massive graphic-rich print job starts printing as soon as the print button is clicked, but 20 people printing a blank word document stalls the printer. Multiple print jobs can be sent from 1 computer with no problem, but single jobs from multiple different computers kills the printer for a few hours.
The workstations are all set up to print directly to the printer’s IP address. We are currently using the newest available 4510 PCL6 windows 7 driver (not the global driver), but the PostScript driver produced the same problem. The printer firmware is also the newest version.
Or, if there is no solution, does anyone know the maximum number of simultaneous print jobs the 4510’s built-in print server can handle?
The Phaser 4510 should accept up to 6 simultaneous sockets and then flag the remaining as “busy”. This way the first 6 are spooled up and start printing, but the remaining stay in a “busy” state until there is an open socket. This is over Port 9100 or LPR.
I hope this helps,
What do you recommend for a Phaser 6180 that stalls/hangs when multiple print jobs are being sent to it from a jounalism class with 15 Mac's OSX 10.6.8 The Phaser has 128mb memory.
If you're sure it's not an issue with the Mac OSX 10.6.8 which was an issue that was a very hot topic a couple of months ago in this forum - My suggestion is that you call Xerox and request to speak to someone in 2nd Level Support. Explain to them what your situation is and they can begin to suggest possible solutions. First though, check this forum for the Mac 10.6.8 issue. I think it was the same sort of thing you're seeing. Print jobs hanging in the queue. There is a fix and somebody posted what it was and how to get it.