Red Hat Bugzilla – Bug 202977
smbspool should percent-decode DEVICE_URI
Last modified: 2007-11-30 17:11:40 EST
Description of problem:
When trying to print using cups to windows Print share (Password Protected),
backend smb fails with following message
backend smb failed.
ERROR: Tree connect failed (NT_STATUS_ACCESS_DENIED)
ERROR: Unable to connect to CIFS host, will retry in 60 seconds...
Password security is implemented at our side and we must use special characters
in the password. The password contains "#" at the end. For e.g. test123#
Here is the DeviceURI Line in printers.conf file.
Insted of using smb linked to smbspool i created a shell script to display
DEVICE_URI and found that
CUPS is truncating the DEVICE_URI after #
I have tried to use Hex character %23 for # however in that case samba can not
authenicate against windows printer share.
So to summarize the issue here is
1. Use of password protected Windows Print Share
2. Use of special characters # in the password
3. Use Samba
4. cups will truncate DeviceURI and only conains string before #. (printing
fails). Escaping it with \# also does not work.
5. if used %23 instead of #, samba will not authenticate against Printer share.
in either case printing will not work.
Only workaround is to write shell script and explicitly export DEVICE_URI
environment variable and name it as smb.
smbpool $1 $2 $3 $4 \"$5\"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure CUPS to connect to Windows network printer share with password
containing # at the end.
2. Try printing to it using echo test | lp -d printername
3. check for error log in /var/log/cups/error_log
No print output
I've asked upstream about this:
The # needs to be % encoded, as required by the URI spec...
Reassigning to samba because of above:
"5. if used %23 instead of #, samba will not authenticate against Printer share."
Created attachment 134439 [details]
Try this patch.
When this Patch will be incorporated in samba-client Package. Current version of
Samba-client package is : samba-client-3.0.23b-2. If i have to apply this patch
today, Will i have to download the source package myself, apply the patch and
recompile it to make it work again.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
This patch is still needed. See https://bugs.launchpad.net/bugs/105022 for
another instance of this.
moving to FC6, then. Thanks.
I am working on a patch
See patch attached here: https://bugzilla.samba.org/show_bug.cgi?id-2319
Patch works here.
This is fixed upstream and should be already fixed in F7/F8