Bug 4349 - Cannot use windows printer via Samba (problems with password containing # character)
Cannot use windows printer via Samba (problems with password containing # cha...
Status: RESOLVED FIXED
Product: Samba 3.0
Classification: Unclassified
Component: Printing
3.0.22
x86 Linux
: P3 major
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-20 16:02 UTC by Sergey Pisarenko
Modified: 2012-01-09 11:01 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Pisarenko 2007-01-20 16:02:54 UTC
ORIGINAL POST ON CUPS BUGZILLA (HOWEVER, SEEMS LIKE A SAMBA PROBLEM):

When I try to configure my SAMBA printer in CUPS I specify this address:
smb://pisarenk:z7#TD2qm@print/ituniv4-east

But my password contains "#" character. If I enter it directly, then printing works until first restart. After restart the link in CUPS gets cut to something like smb://pisarenk:z7. If I replace the "#" character with "%23" I cannot use the printer. CUPS says that it cannot connect to CIFS.

Part of log:
E [20/Jan/2007:18:07:51 +0100] [Job 34] Session setup failed: NT_STATUS_LOGON_FAILURE
E [20/Jan/2007:18:07:51 +0100] [Job 34] No ticket cache found for userid=1000
E [20/Jan/2007:18:07:51 +0100] [Job 34] Can not get the ticket cache for drseergio
E [20/Jan/2007:18:07:52 +0100] [Job 34] Session setup failed: NT_STATUS_LOGON_FAILURE
E [20/Jan/2007:18:07:52 +0100] [Job 34] Tree connect failed (NT_STATUS_ACCESS_DENIED)
E [20/Jan/2007:18:07:52 +0100] [Job 34] Unable to connect to CIFS host, will retry in 60 seconds...

I suspect that it is partly connected to CUPS but rather to Samba, however, I am not sure what to do to fix this.

CUPS 1.2.6
samba 3.0.22-r3

ANSWER FROM CUPS SUPPORT:

This is not a CUPS problem.

Please report this bug to the Samba folks, who will need to fix their smbspool program so that it supports % encoding in the URI.
Comment 1 Andreas Schneider 2012-01-09 11:01:47 UTC
This is probably fixed with a newer Samba version. If you still see the error. Please open a new bug with 'debug level = 10' logfiles of the new Samba version 3.5 or 3.6. Thanks!