samba - Oct 2007 - Uploading printer driver from Windows client gives "access denied" error

I'm using Samba 3.0 on a Debian Sarge server, and am trying to upload
printer drivers from a Windows client. I connect to the server using the
root credentials (yes I know ...), but every time I get an "access
denied" message when the driver upload process starts. I can perform
other root functions via this connection no problem. I have uploaded
drivers this way in the past but can't figure out why it won't work this
time.

Here's the relevant parts of my smb.conf:

[global]
printing = cups
printcap name = cups
printer admin = root
load printers = yes
[printers]
path = /var/spool/samba
public = yes
printable = yes
guest ok = yes
read only = no
[print$]
path = /var/lib/samba/printers
browsable = yes
write list = root

Can anybody see anything I might be doing wrong here or suggest how I
might narrow down the problem?

Thanks very much.

Tony.

Tony Groves writes:
> I'm using Samba 3.0 on a Debian Sarge server, and am trying to upload
> printer drivers from a Windows client. I connect to the server using the
> root credentials (yes I know ...), but every time I get an "access
> denied" message when the driver upload process starts. I can perform
> other root functions via this connection no problem. I have uploaded
> drivers this way in the past but can't figure out why it won't work
this
> time.
> 
> Here's the relevant parts of my smb.conf:
> 
> [global]
> printing = cups
> printcap name = cups
> printer admin = root
> load printers = yes
> [printers]
> path = /var/spool/samba
> public = yes
> printable = yes
> guest ok = yes
> read only = no
> [print$]
> path = /var/lib/samba/printers
Do you have the COLOR, W32X86 and WIN40 directories created in 
/var/lib/samba/printers? I think there are even others, for 64bit version of 
windows and the like..

Otherwise, have a look at the logs. Easiest way to do this is to do 
everything until uploading the driver and then increasing the log file with 
'smbcontrol smbd debug 3'. Maybe you need to do this with different 
(higher) log levels to get the right info.

Good luck!

-r

> > From: Roel van Meer <rolek@alt001.com>
> > 
> > Tony Groves writes:
> > 
> > > I'm using Samba 3.0 on a Debian Sarge server, and am trying
to upload
> > > printer drivers from a Windows client. I connect to the server
using the
> > > root credentials (yes I know ...), but every time I get an
"access
> > > denied" message when the driver upload process starts. I can
perform
> > > other root functions via this connection no problem. I have
uploaded
> > > drivers this way in the past but can't figure out why it
won't work this
> > > time.
> > > 
> > > Here's the relevant parts of my smb.conf:
> > > 
> > > [global]
> > > printing = cups
> > > printcap name = cups
> > > printer admin = root
> > > load printers = yes
> > > [printers]
> > > path = /var/spool/samba
> > > public = yes
> > > printable = yes
> > > guest ok = yes
> > > read only = no
> > > [print$]
> > > path = /var/lib/samba/printers
      browsable = yes
      write list = root
> > Do you have the COLOR, W32X86 and WIN40 directories created in 
> > /var/lib/samba/printers? I think there are even others, for 64bit
version of
> > windows and the like..
> > 
> > Otherwise, have a look at the logs. Easiest way to do this is to do 
> > everything until uploading the driver and then increasing the log file
with
> > 'smbcontrol smbd debug 3'. Maybe you need to do this with
different
> > (higher) log levels to get the right info.
> > 
Yes, the directories are all there. The driver is the Windows 2000
version, and as far as I know, uses the W32X86/2 directory. W32X86/3 is
already in use by two other printers.

Now, the log files. I upped the debug level to 3 and extracted the log
entries corresponding to the time from when I clicked OK to when the
error message appeared. Unfortunately I can't make head nor tail of it.
I've uploaded the file to http://tongro.org/tmp/log.smbd . There's a lot
of text there, but maybe somebody might spot something.

Thanks for the help.

Tony.

From: Dale Schroeder
<dale@BriannasSaladDressing.com>
> If what I described above does not work for you, perhaps this thread
> applies?
> 
>
http://archives.devshed.com/forums/samba-120/problems-installing-printer-driver-1365160.html
> 
That seems to do the trick, thanks. The driver files were read-only, but
after I enabled write access I was able to install them. That seems
strange; why would Samba need write access to driver files? And anyway,
can it not change permissions if needed? Anyway, there's no point
wondering, it works now.

From: Peter Ulrich <Peter-Ulrich@web.de>
> When i give the User Administrative rights, then i was able to upload
> Printer-Drivers.
Thanks. I think the user does have full rights on the client machine, but 
I didn't need that in the end.


I have another problem now though. I can connect to the printer from a
Windows client, but whenever I try printing to it, the client machine 
suddenly reboots. That's a separate issue I suppose; I'd better gather a
bit more information before presenting it here.

Thanks again.

Tony.