I just wanted to make it clear, that I think all my problems are stemming
from not being able to connect to the samba server as an admin account. both
"root" and "panderson" are in the smbpasswd file, with valid
passwords that
I set. I just can't get authenticated as either user, unless I explicitly
set a share to not allow access to anyone but one of those users. I.e., the
NT client automatically connects as a non-admin or guest account, even if I
map the share to connect as root.
thanks again,
-Phil Anderson
> -----Original Message-----
> From: Anderson, Phil
> Sent: Thursday, June 27, 2002 3:53 PM
> To: 'samba@lists.samba.org'
> Subject: setting drivers?
>
> Hi!
>
> I'm trying to set drivers for printers such that they will
automatically
> download onto winNT/W2K clients. I've followed the instructions in
> printer_drivers2.html (I'm using samba 2.2.5). my questions:
>
> -do I have to define each printer individually in smb.conf? I know you do
> for the "old" style of printing, the style that didn't work
with NT or
> W2K. here's what I have now:
>
> -->snip
> [global]
> -->snip
> printer admin = panderson
> -->snip
>
> [print$]
> path = /usr/local/samba/printers
> guest ok = yes
> browseable = yes
> read only = yes
> write list = panderson,root
>
> [printers]
> comment = All Printers
> path = /var/spool/lpd
> browseable = yes
> guest ok = yes
> writable = no
> printable = yes
> print command = /usr/bin/lpr -r %s
> printing = BSD
> public = yes
> printer = hp5
> browseable = yes
> read only = yes
>
> [hp5]
> path = /var/spool/lpd/hp5
> printable = yes
> print command = /usr/bin/lpr -r -P%p %s
> printer = hp5
> printing = BSD
> guest ok = yes
> public = no
> browseable = yes
>
> [hp4050_hr]
> path = /var/spool/lpd/hp4050_hr
> printable = yes
> print command = /usr/bin/lpr -r -P%p %s
> printer = hp4050_hr
> printing = BSD
> guest ok = yes
> public = no
> browseable = yes
>
> -I read the paragraph in printer_driver2.html as follows:
>
> [==begin paste==]
> Once you have created the required [print$] service and associated
> subdirectories, simply log onto the Samba server using a root (or printer
> admin) account from a Windows NT 4.0/2k client. Open "Network
> Neighbourhood" or "My Network Places" and browse for the
Samba host. Once
> you have located the server, navigate to the "Printers..."
folder. You
> should see an initial listing of printers that matches the printer shares
> defined on your Samba host.
> Setting Drivers for Existing Printers
> The initial listing of printers in the Samba host's Printers folder
will
> have no real printer driver assigned to them. By default, in Samba 2.2.0
> this driver name was set to NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER.
> Later versions changed this to a NULL string to allow the use tof the
> local Add Printer Wizard on NT/2000 clients. Attempting to view the
> printer properties for a printer which has this default driver assigned
> will result in the error message:
> Device settings cannot be displayed. The driver for the specified printer
> is not installed, only spooler properties will be displayed. Do you want
> to install the driver now?
> Click "No" in the error dialog and you will be presented with the
printer
> properties window. The way assign a driver to a printer is to either
> * Use the "New Driver..." button to install a new printer driver,
or
> [==end paste==]
>
> I'm connecting from a NT4 client. My samba server never asks me for a
> password, and I've done everything I know (map the server with a
different
> username, etc) and I can't get the server to ask me for a password.
This
> is a problem, because when I right-click on the printers (on the samba
> host through winNT), I can't set drivers for them, as the options are
all
> grayed out (due to lack of permissions.) My username is in the smbpasswd
> file, and I know it authenticates right, because I can get access to my
> home dir through the samba share. I just can't get the printers share
> mapped with a different username (mapping \\hostname\print$ works, but
> mapping \\hostname\printers raises a "network name not found"
error.)
>
> I've been working on this for numerous hours, and I don't know why
it's
> happening. Any help would be greatly appreciated. Thanks,
>
> -Phil Anderson
>
