RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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

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

I am using the Microsoft Postscript driver

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