[Samba] cups / samba job control issue

Tim Kelley initech at it.kpt.cc
Wed Nov 24 00:58:23 GMT 2004

Hi all,

I am using cups 1.1.22 with samba 2.2.12 along with winbind, and samba
configured as a domain member. For now I'm not able to switch to samba3.

My problem is that users printing from windows are unable to control
their jobs. Pause, resume or cancel do not work. In windows, the
"error processing command" is returned. In cups, when viewing
/var/log/cups/access.log, I'll see a line like:

localhost - - [23/Nov/2004:15:02:59 -0600] "POST /jobs HTTP/1.1" 401 0

"401" error code indicating "unauthorized". Also note there is no
username in the second field, indicating the username was not passed
from samba to cups(?), which I think is the heart of the problem.

I notice that even though I have:

        winbind enum users = Yes
        winbind enum groups = Yes
        winbind use default domain = Yes

 ... that "smbstatus" still appends my DOMAIN+ in front of the username -
although "getent passwd" or "wbinfo -u" do not. 

When jobs are submitted, this works - I'll see the the username
properly in cups:

laserjet-queue username 567 [23/Nov/2004:15:19:50 -0600] 1 1 - winpc

In samba I get the following in the logs when attempting to manipulate
a  (my own) job:

[2004/11/23 15:56:25, 0] printing/print_cups.c:cups_job_delete(482)
  Unable to cancel job 566 - client-error-not-authorized
[2004/11/23 15:56:40, 0] printing/print_cups.c:cups_job_pause(572)
  Unable to hold job 569 - client-error-not-authorized

I have in [global]

printing = cups
printcap name = cups

I have tried expressly defining the lp commands in my [printers] but
that does not help either (it's my impression printing = cups does not
use that). This seems clearly an auth problem ...

In cups, I have for:
<Location /jobs>
AuthType Basic
AuthClass User

What do I need to do to give users control over their print jobs? If I
login to the print server (say, via ssh) with a windows domain
account, I can control my print jobs just fine.

I don't think this has anything to do with pam, pam is working fine
and I can log in to this machine with a windows account and get a

If you wish to see the (sanitized) smb.conf for this system, please see


More information about the samba mailing list