automatically setting up printer drivers on clients (new style)

[Gerald Carter]

On 25 Jan 2002, Nick Pietraniec wrote:

> I've got a Windows NT Domain "WHEELZ" which I've sucessfully joined
> (users connect to my shares w/no problem) but it doesn't seem like my NT
> admin accounts are getting admin permissions.  I'm trying to browse to
> the printers folder on a 2k box and run the add printer wizard to add
> drivers for the printer.  If I log on as administrator, browse to the
> printer, and do properties->sharing tab, click "add additional drivers,"
> and I try to add drivers for NT 4.0 (intel) I get the error
>
> The "Add printer" button is also not appearing, and, I'm not able to
> write to the "print$" share... 

The APW icon appears when you are able to connect to the Samba server
(or NT/2k print server for that matter) and issue a OpenPrinterEx()
RPC with SERVER_ACCESS_ADMINISTER rights.

Remember that in order for the APW to work, you need to define
an "addprinter command" script in smb.conf.  If you have already defined 
the printers in smb.conf, you can bind drivers to the printers by choosing 
the drop down driver list in the printer properties dialog (or uploading a 
new driver via the "New Driver..." button).

If you are uploading a new driver to an existing printer and get "Access 
Denied", there are two common reasons

  *) unable to write to [print$] (you say you can do this)

  *) unable to write to the nt*.tdb files (this can only be done
     by root or by a "printer admin"


> However, I've created a user "root" in my domain, and if I log on using
> that user, the "add printer" button appears and I'm able to write to the
> print$ share, but when I try to add the additional drivers I get
>
> Unable to install the Intel, Windows NT 4.0 or 2000 driver.  Operation
> could not be completed

Is root a "Domain Admin"?  If I understand you correctly, then I think I 
know what is going on....

You are logged into the Win2k as WHEELZ\root.  First off, if you are 
running winbind, then this will not be mapped to root(uid 0) if I am 
remembering correctly.  If you are not running winbind, then it should be 
mapped to the local root account as your are expecting.

(since you say that you see the APW icon and since there are no winbind 
 related parameters in your smb.conf, I'm guessing you are not running 
 winbind.)

Second question, have you already installed the Win2k drivers on the 
server?  You need to do this before adding any additional client drivers.


> I have created the print$ share properly (since I'm able to browse to
> it) and it's owned by root.  Inside I've created a "WIN40" directory and
> a "W32X86" directory.

Let me know of this helps. If not, I'll need some more specifics
(probably log files).


> [global]
> 	workgroup = WHEELZ
> 	netbios name = psnc9600
> 	server string = Samba rules.
> 	security = DOMAIN
> 	encrypt passwords = YES
> 	null passwords = No
> 	obey pam restrictions = No
> 	password server = REASONER BUZZ
> 	smb passwd file = /etc/samba/smbpasswd
> 	name resolve order = hosts wins lmhosts bcast
> 	time server = No
> 	load printers = Yes
> 	printcap name = /etc/printcap
> 	wins server = 192.210.21.104
> 
> 	guest account = nobody
> 	
> 	printer admin = @ntadmin
> 






chau, jerry
 ---------------------------------------------------------------------
 Hewlett-Packard                                     http://www.hp.com
 SAMBA Team                                       http://www.samba.org
 --                                            http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN 0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--