Bug 3135 - Add Printer Wizard Driver Installation. Fails with access denied.
Summary: Add Printer Wizard Driver Installation. Fails with access denied.
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Printing (show other bugs)
Version: 3.0.20
Hardware: Sparc Solaris
: P3 normal
Target Milestone: none
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-04 09:45 UTC by Andrew Watkins
Modified: 2005-10-06 06:13 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Watkins 2005-10-04 09:45:20 UTC
I had been using 3.0.11 and added a lot of printers following the info at
"Chapter 20. Classical Printing Support" using the "Add Printer Wizard Driver
Installation"  on XP client.

I went to add some more printers using version 3.0.20 (upgraded a while ago) and
it gives me errors:
Procedure:
- Open Windows Explorer, browse to the Samba host, open Samba's Printers folder,
right-click on the printer icon, and select Properties and select "No"
- Select printer Driver
- It copies driver files to server
- Apply settings and you get "Printer setting could not be saved. Access is denied."

I have not altered my smb.conf
....
printer admin = andrew
[print$]
        comment = Printer Driver Download Area
        path = /usr/local/samba/var/drivers
        browseable = no
        guest ok = no
        read only = yes
        write list = andrew

I went back to 3011 and it did all wotk again and 3020a did not seem to help me...

Any thoughts. It may be that the HOW TO is out of date now.

Thanks

Andrew
Comment 1 Gerald (Jerry) Carter (dead mail address) 2005-10-05 07:26:32 UTC
The driver upload process has not changed with the 
exception of of using the SePrintOperatorPrivilege
rather than the 'printer admin' parameter.

Can you attach (not an inline comment) gzipped a level 10 
smbd debug log of the failure?  Thanks.
Comment 2 Andrew Watkins 2005-10-06 06:13:33 UTC
WHOPS!

I think it is user error. I just noticed that I had added one line to the
smb.conf "use client driver = Yes" which reading the manual pages may cause 
the problem. If I set "use client driver = No" then all works fine.

Sorry for wasting any ones time...

Andrew