On 12/11/08 12:20 PM, "Terry Spaulding" <[email protected]> wrote:
> We found a printer that did not support IPP so we had to define the printer > on the Win/XP desktop as an LPR. It works fine as an LPR. > We also found a printer that only partially supported IPP and that one we > had to define as LPR. The printers do not have to support IPP at all. That's why you define the printers to the *CUPS server* as LPR printers, not have the clients bypass the CUPS server and talk to the printers directly, which (unless I'm missing something entirely) is what the setup you're describing seems to do. > Now the final part of this is to setup the ability to easily add these > SAMBA printers to Win/XP desktops. > If I understand correctly anyone should be able to open a browser to the > SAMBA Linux guest and be presented with a display of the known > printers on SAMBA/Cups point to one and click. A ppd file will be created > and the printer added to the Win/XP desktop. The point-and-print support in Samba downloads the appropriate printer driver from the Samba server and installs it on the client with the proper remote port defined. It does not create a PPD file unless the Windows printer driver uses the Adobe PPD framework. > "samba1:/var/lib/samba/drivers/W32X86 # cat 'password for cupsadm required > to access localhost via SAMBA:' > WARNING: The "printer admin" option is deprecated > SetPrinter call failed! > result was WERR_ACCESS_DENIED > WARNING: The "printer admin" option is deprecated > failed session setup with NT_STATUS_LOGON_FAILURE > Cannot connect to server. Error was NT_STATUS_LOGON_FAILURE > Running command: rpcclient localhost -N -U'cupsadm%samba' -c 'setdriver > AUDIT01-HP-136.020 AUDIT01-HP-136.020' The logon failure indicates that the Samba server was unable to authenticate the user that is running the command as a printer admin. Make sure that the userid is added to the Unix group you defined as the printer admin group, or that winbind is able to access AD to get the Windows group information correctly if Samba is not acting as a domain controller. A suggestion: use a Windows server to upload the drivers. The printer admin tools on the Windows servers tend to be more reliable than the standalone utilities. Also check out wiki.samba.org/index.php/Samba_as_a_print_server Note ownership of the directory structure and the script to create the correct structure. There is also detailed information on setting up CUPS with Samba in the CUPS Software Administrators Manual in the documentation for the cupsaddsmb command (see http://www.cups.org/documentation.php/doc-1.4/man-cupsaddsmb.html) ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
