I am now getting around to setting up a test printer. CUPS is installed in RAW mode and a test print work A-OK. I also set the CUPS printer que as default. Below are my printer related smb.conf lines for this PDC. [global] ... ########## NT Domain Related ########## admin users = pianoman ldsinst ... ########## Printing ########## printcap name = CUPS printing = CUPS [printers] comment = SMB Print Spool path = /var/spool/samba printable = Yes guest ok = Yes read only = no use client driver = Yes browseable = No create mode = 0600 ... And I did create /var/spool/samba as follows: mkdir /var/spool/samba chmod 0777 /var/spool/samba chmod o+t /var/spool/samba I am logged it with both local Admin permissions on the Win2K client and domain admin in Samba, per above. Ideas why when going through the add printer wizard, browsing, touching the que it says access denied? TIA! -- Michael Lueck Lueck Data Systems Remove the upper case letters NOSPAM to contact me directly.
Michael Lueck
2004-Jul-09 17:42 UTC
[Samba] Re: Access Denied touching shared CUPS printer
Most Ugly! In Google'ing around it seems this "Access Denied" is a known issue with Win2K/XP clients, CUPS printers, etc... So, use printerui.dll to force install the printer driver and assign to a local LPT1 port. Add a port registry key, and the update the port in two spots under the printer instance. Finally stop/start the spooler task. Scrptable yet ugly. Most Ugly! Ah, Samba team... does this topic need some pizza applied to it? Please advise. What's the bug anyway? Something to do with CUPS? It seems there are not "lots" of people bumping into this, thus makes me think other printing methods are not affected. I was quite pleased with HOW EASY this setup was going along, until slamming into the Access Denied issue. RAW spooling looked way cool, Samba enum'ing the CUPS queues, etc... -- Michael Lueck Lueck Data Systems Remove the upper case letters NOSPAM to contact me directly.