I am quite keen to use the APW at this site because the admin is a die hard Windows/GUI user and freezes up like a deer in the headlights whenever 'terminal' is mentioned!
Would it be better to use another printing subsystem?
Also, is there any way to make the printers on the samba server just 'links' to the ip printers? IE when clients connect they download the drivers and then print directly to the printers ip, not the samba server.
Thanks again,
Hamish
Kurt Pfeifle wrote:
Message: 19 Date: Wed, 14 Apr 2004 12:54:02 +0100 From: Hamish <[EMAIL PROTECTED]> Subject: [Samba] Add printer wizard (XP) To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii; format=flowed
Hello list
I have been really wowed by samba 3 so far, i just have one last mission to complete... please help!
I have samba 3.0.2a-SuSE installed on a SuSE 9.0 box. It uses winbind to authenticate against a win server 2003 box - this seems to work fine, users can own files and this is shown when getfacl is run on the shares (owned by DOMAIN\User).
The last problem i have is adding printers...
The add printer wizard shows for the windows domain administrator, and he can add a printer right untill the last screen of the wizard - when he clicks the finish button, it shows the error:
Add Printer Wizard Unable to Install Printer. Access is denied.
You need 2 things for this to work:
1.) a setting in smb.conf "add printer command = /path/to/smb-add-printer-script.sh"
2.) an actual "smb-add-printer-script.sh" script in named path
So far, I don't know of anyone who has written a reliably working "add printer command" script which works with CUPS.
By own efforts got stuck some time ago because of a weird re-naming problem
(Samba re-named my newly created printer because it executed the script a
2nd time somehow....)
I will probably revisit that topic within the next few weeks.
The point is that the script needs to take the variables to run CUPS "lpadmin"
from what the user filled into the "Add Printer Wizard" fields....
The only thing i can think of is that he has no permission to add a cups printer? The driver files are correctly copied across to PRINT$, but then straight after this the error appears.
The usefulness of the "APW" for you (without the "add printer command") is
currently limited to add new drivers and for existing printqueues....
Here is my smb.conf:
It misses the "add printer command" line....
[global] workgroup = MYDOMAIN server string = samba test security = DOMAIN password server = pwdserver log level = 1 syslog = 0 socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY printcap name = CUPS os level = 2 preferred master = No local master = No idmap uid = 10000-20000 idmap gid = 10000-20000 admin users = MYDOMAIN\administrator printer admin = MYDOMAIN\administrator printing = cups veto files = /*.eml/*.nws/riched20.dll/*.{*}/
Cheers, Kurt
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
