Hello, I have a CentOS 4.4 box acting as a print server with a cups backend and samba 3.2.4. I recently ran yum which updated both cups and cups-libs, but i do not think this is my problem. I've added windows drivers to the samba sharea and have in the past printed a test page to the printer. Now when i atempt to do this with a word document from a windows box, i am getting the error: client not authorized. It is showing me connecting to the print$ share as my user which have SePrintOperatorPrivilege, then i get the error from cups about the client not being authorized. Any help appreciated. Thanks. Dave.
On 4/20/07, Dave dmehler26@woh.rr.com wrote:
Hello, I have a CentOS 4.4 box acting as a print server with a cups backend and samba 3.2.4. I recently ran yum which updated both cups and cups-libs, but i do not think this is my problem. I've added windows drivers to the samba sharea and have in the past printed a test page to the printer. Now when i atempt to do this with a word document from a windows box, i am getting the error: client not authorized. It is showing me connecting to the print$ share as my user which have SePrintOperatorPrivilege, then i get the error from cups about the client not being authorized. Any help appreciated. Thanks. Dave.
I have a similar setup except that samba is 3.0.10. In my case, I have a guest account for samba and the print jobs are queued from samba to cups as this user. This has been working well under CentOS 4.4.
Akemi
Akemi Yagi wrote:
On 4/20/07, Dave dmehler26@woh.rr.com wrote:
Hello, I have a CentOS 4.4 box acting as a print server with a cups backend and samba 3.2.4. I recently ran yum which updated both cups and cups-libs, but i do not think this is my problem. I've added windows drivers to the samba sharea and have in the past printed a test page to the printer. Now when i atempt to do this with a word document from a windows box, i am getting the error: client not authorized. It is showing me connecting to the print$ share as my user which have SePrintOperatorPrivilege, then i get the error from cups about the client not being authorized. Any help appreciated. Thanks.
I have a similar setup except that samba is 3.0.10. In my case, I have a guest account for samba and the print jobs are queued from samba to cups as this user. This has been working well under CentOS 4.4.
Do either of you see anything in /var/log/messages with "cups" in it?
grep cups /var/log/messages
On 4/24/07, Ben Russo ben@muppethouse.com wrote:
Akemi Yagi wrote:
On 4/20/07, Dave dmehler26@woh.rr.com wrote: I have a similar setup except that samba is 3.0.10. In my case, I have a guest account for samba and the print jobs are queued from samba to cups as this user. This has been working well under CentOS 4.4.
Do either of you see anything in /var/log/messages with "cups" in it?
My server is set up to take print jobs from Mac and Unix/Linux boxes in addition to Windows. I see "cups" in the messages file only when someone sends jobs using the lp facility. The server has cups-lpd enabled, so:
Apr 23 12:02:57 info-svcs cups-lpd[15602]: Connection from [client machine name] Apr 23 12:02:57 info-svcs cups-lpd[15602]: Receive print job for DeptColorPrinter Apr 23 12:02:58 info-svcs cups-lpd[15602]: Print file - job ID = 3183 Apr 23 12:02:58 info-svcs cups-lpd[15602]: Closing connection
This particular example is a job from a Mac. Other than these lines, I do not see any lines containing "cups".
Akemi