Printing to an Oce 31x5
John A. Murdie
john at cs.york.ac.uk
Fri Aug 12 09:50:31 PDT 2005
I've been unable to configure CUPS 1.1.23 on Solaris 9 for printing to ourOce 31x5 printers - even though it works smoothly with various HP printers. I think I might be getting the printer URIs wrong.
Oce referred me to their document "Printer Drivers : Printer Driver Installation" on their web site - from http://www.oce.co.uk/; click 'Support and Downloads'; 'Contact Oce UK Support for downloads'; 'Downloads' (under 'Other support options'); 'Printer drivers'; select Product '3165', Title 'PostScript Drivers 31x5' and press 'Go'; at top right under 'Related information' click 'Printer Driver information' to open a PDF document. Phew!
On page 9 of that document (under 'Installation Instructions for Windows 2000/XP/2003 - IPP') the recommended form of printer URI is either:
(for a print server that uses Microsoft IIS) or:
(for a print server that uses Apache). Oce said that any queuename would do. (Yes, of course I substituted our actual values for the place-holder names above.)
Oce assure me that IPP is permanently enabled on 31x5 printers. They work fine with the Berkeley LPR print system (using the RFC1179 LPR print protocol).
I created this printer with the CUPS web admin interface using each of the above URIs in turn. I've also tried both forms without a queuename. For each, I see the message:
"Printer State: processing, accepting jobs.
Network host 'ourprinter.oursite.ourtld' is busy; will retry in 30 seconds..."
There's nothing in the CUPS error_log that apparently refers to errors from the IPP backend other than:
I [12/Aug/2005:17:40:46 +0000] [Job 8] Connecting to ourprinter.oursite.ourtld on port 631...
I [12/Aug/2005:17:40:46 +0000] [Job 8] Network host 'ourprinter.oursite.ourtld' is busy; will retry in 30 seconds...
- I have 'LogLevel debug2' turned on in cupsd.conf (and cupsd restarted to effect this).
Another thing which worries me a little is that the CUPS page_log file shows that the various test pages have all been printed, even though no paper has come out of the printer, and nothing has been retained in the printer's 'mailbox' for subsequent release and printing.
Any idea what is going on?
John A. Murdie
Department of Computer Science
University of York
More information about the cups