Bug 640888

Summary:	cupsaddsmb results in WERR_UNKNOWN_PRINTER_DRIVER
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Stark <cstark>
Component:	samba	Assignee:	Guenther Deschner <gdeschner>
Status:	CLOSED ERRATA	QA Contact:	Ales Zelinka <azelinka>
Severity:	high	Docs Contact:
Priority:	low
Version:	6.0	CC:	antillon.maurizio, azelinka, dpal, gdeschner, ssorce, twaugh
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	samba-3.5.4-70.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-19 13:14:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Stark 2010-10-07 02:42:59 UTC

Description of problem:
After successfully configuring a printer via 'system-config-printer', I am unable to use the cupsaddsmb command successfully. Restarting cups and/or samba, nor rebooting the system helps. The resulting error is always: WERR_UNKNOWN_PRINTER_DRIVER. I have tried to manually run the failing "rpcclient ... -c 'adddriver ...'" command with the same result.

Version-Release number of selected component (if applicable):
RHEL 6 Server Beta x86_64
cups-1.4.2-33.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure printer using system-config-printer
2. run 'cupsaddsmb -v -U username printername' or 'cupsaddsmb -v -a -U username'
  
Actual results:
The command spirals into a never-ending loop of failure stemming from the failed rpcclient/adddriver command and resulting WERR_UNKNOWN_PRINTER_DRIVER error

Expected results:
Successful adding and association of the CUPS Windows driver

Additional info:
The server is configured with samba-3.5.4-65, samba-client, samba-common, and samba-winbind. The system is joined to our AD, and a 'getent passwd' produces a list of all of our AD users. The system is configured nearly identically to a fully functional RHEL 5 print server on our network.

Comment 2 Tim Waugh 2010-10-13 14:40:16 UTC

The fact that rpcclient fails in the same way makes it look like a samba issue.

Comment 6 Guenther Deschner 2010-11-30 10:36:54 UTC

Which Postscript driver are you using ? The Adobe Postscript driver or the Microsoft Postscript driver ?

Comment 9 Chris Stark 2010-12-01 02:54:01 UTC

I am using the Microsoft Postscript driver

Comment 12 errata-xmlrpc 2011-05-19 13:14:26 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0582.html