From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
I have without success tried to print to a samba printer share on a
Win2K server from applications running under Fedora Core 1.
I have verified that the server share is up and running and
connectable from the Fedora client by two means:
# smbspool smb://UID:Password@HC50417/HPLJ1200 1 user title 1 ''
# cat test.txt | smbclient //HC50417/HPLJ1200 Password -c "print -"
in both cases the output was as expected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up Windows SMB printer in redhat-config-printer-gui or -tui as
2. Print test page or print from application
Actual Results: No printing from SAMBA host printer
Expected Results: Printing from SAMBA host printer
Error in Printer configuration: "Unable to connect to SAMBA host, will
retry again in 60 seconds ... ERROR: Connection failed with error
Here is some addition info:
# grep ^DeviceURI /etc/cups/printers.confDeviceURI
# rpm -q redhat-config-printer
# rpm -V redhat-config-printer
SM5....T c /etc/alchemist/namespace/printconf/local.adl
Similar, but not identical, problems have been reported previously in
bug# 80717 and 104136
Created attachment 96725 [details]
Content of /var/log/cups/error_log
This is definitely not the same as bug #80717, since printers.conf has
the correct DeviceURI line. It also looks different to bug #104136,
since the smbspool command line succeeds.
Something is going wrong in between CUPS starting smbspool as the
backend, and smbspool parsing its URI. Perhaps it is something to do
with weird characters like spaces or quotes in the username or password?
There is no weird characters in username or password, just plain
letters and numbers, mixed upper and lower case. Perhaps password is
converted to all-UC or all-LC by some component.
No, it isn't.
Can you try running smbspool directly, giving it the same URI as in
the printers.conf file?
Fedora Core 1 is maintained by the Fedora Legacy project for security updates
only. If this problem is a security issue, please reopen and reassign to the
Fedora Legacy product. If it is not a security issue and hasn't been resolved in
the current FC5 updates or in the FC6 test release, reopen and change the
version to match.
NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy
project. After Fedora Core 6 Test 2 is released (currently scheduled for July
26th), there will be no more security updates for FC1. Please use these next two
weeks to upgrade any remaining FC1 systems to a current release.
Closed per above message and lack of response. Note that FC1 and FC2 are not even
supported by Fedora Legacy anymore.