|
Tip
Try this from a Windows 200x/XP DOS box command prompt:
runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\
SAMBA-SERVER
\
printersharename
Click on Printing Preferences.
... contains the setting
show add printer wizard = yes (the
default).
The APW can do various things:
-
Upload a new driver to the Samba
[print$]
share.
-
Associate an uploaded driver with an existing (but still driverless) print queue.
-
Exchange the currently used driver for an existing print queue with one that has been uploaded before.
-
Add an entirely new printer to the Samba host (only in conjunction with a working
add printer command. A corresponding
delete printer command for removing entries from the
Printers folder may also be provided).
The last one (add a new printer) requires more effort than the previous ones. To use the APW to successfully
add a printer to a Samba server, the
add printer command must have a defined value.
The program hook must successfully add the printer to the UNIX print system (i.e., to
/etc/printcap, /etc/cups/printers.conf or other appropriate files)
and to smb.conf if necessary.
When using the APW from a client, if the named printer share does not exist, smbd will execute the
add printer command and reparse to attempt to locate the new printer share. If the
share is still not defined, an error of "Access Denied" is returned to the client. The
add printer command is executed under the context of the connected user, not
necessarily a root account. A
map to guest = bad user may have connected
you unwittingly under the wrong privilege. You should check it by using the
smbstatus
command.
|
