Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: compsos on April 10, 2005, 04:30:12 AM

Title: Samba 3 and Cups
Post by: compsos on April 10, 2005, 04:30:12 AM
Hi

Has anyone found a solution to CUPS reporting
"Sending error: client-error-nor-found"?
The job leaves the client but does not register with CUPS. Printing a test page from the CUPS/Printers page is fine.
The only reference that I have found was at samba.org and that it is solved in Samba 3.0.8. Has anyone tried 3.0.8 samba files on 6.0.1-01?
Title: Samba 3 and Cups
Post by: irian on April 10, 2005, 12:35:12 PM
you need to set up you printers in Cups with Driver and Queue = raw.
You need to install the driver on the wks yourself.
Then all should work fine.
Title: Samba 3 and Cups
Post by: compsos on April 13, 2005, 01:59:00 AM
Thanks Irian

Yes I did try that but got 4 pages from the "Print Test Page" on the Cups screen. 3 were blank and the last just a small bit of garbage.
Title: Samba 3 and Cups
Post by: Robert on April 13, 2005, 06:51:10 PM
Actually, using a raw queue is not required. The following document describes methods for printing to what I call "filtering queues" and quite a few of them are for Windows clients: http://mirror.contribs.org/smeserver/contribs/rvandenaker/beta/e-smith-cups/documentation/howtos/printing-to-filtering-queues.html .

Irian, the garbage you see when you print the CUPS test page using a raw queue is PostScript. As it says in http://mirror.contribs.org/smeserver/contribs/rvandenaker/beta/e-smith-cups/documentation/howtos/cups-add-printer.html in the section about raw printers: "Please note that printing a test page will fail on non-PostScript printers. This is because you're sending a PostScript test page to the printer raw. " A failed test print in this case does not indicate that the raw queue won't work.

Anyways, if the problem were a driver/queue type mismatch, the error you'd probably see is "Unable to convert file 0 to printable format" and not what you reported. What I'd do is first check if your installation isn't borked (the command "which lp" is a good first test for this). If it isn't, increase LogLevel to "debug" in /etc/cups/cupsd.conf, reload cupsd, and see if that gets you anything useful.