From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
I have a shared printer under Windows XP. I wanted to print on the
printer from Windows XP. N specific userid is required to print on
the printer from XP (in fact, I am not sure how to set that up - I am
able to check "shared" or "not shared".
I reied setting up the printer with CUPS directly, using the "web"
interface, and I tried setting up the printer using
redhat-config-printer. The smbspool command, used under the covers by
CUPS, produced the following error message and never allowed the file
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a Windows XP system
2. Configure an attached printer
3. Try to print on the printer using
In all cases, I was able to reduce the problem to what you see when
you use this command:
[root@quickdraw log]# smbspool smb://MAID/GATEWAY/HPOffice a b c d e
failed tcon_X with NT_STATUS_ACCESS_DENIED
ERROR: Connection failed with error NT_STATUS_ACCESS_DENIED
ERROR: Unable to connect to SAMBA host, will retry in 60 seconds...
I hit contol C to get out of the program - it would sit and retry once
a minute forever.
Changing the command as follows:
[root@quickdraw log]# smbspool smb://guest@MAID/GATEWAY/HPOffice a b c
d e secure
allows the command to work.
Expected Results: I expected the file to print. I believe that there
is some incompatability between how smbspool hanles the case where no
specific userid and password is required by windows to access a
printer and the way Windows XP deals with the problem.
There is a similar issue when you try to mount shares using autofs.
You have to specify a userid. But between Win98 and XP, there were
some changes made on the windows side and suddenly I had to specify a
username when doing SMB access.
The system called "gateway" above is in the same workgroup (MAID) as
the Linux Box here, and it is on the same ethernet. It may interest
you to know that the guest account is disabled on that system - that
is, it has no guest account at all.
I was able to get the printer I configured via redhat-config-printer
to work simply by specifying a userid of guest in the appropriate
screen, without a password. I was able to get the printer I added via
CUPS to print by specifying the userid in the smb URL.
It is possible that this could be fixed in CUPS or in CUPS and
redhat-config-printer instead of smbspool. I did web searches and
noted that several people had asked this question in various lists and
forums, but I never saw it answered.
I really searched in a lot of places to try and find this bug,
including googling and reading through many summaries and doing very
broad searches. I was doing an additional search to e-mail a couple of
the people who were complaining about this issue in various places on
the web when my searches found
http://rhn.redhat.com/errata/RHBA-2003-276.html and bug 104293 against
However, that bug claims that the bug should be fixed in
redhat-config-printer-0.6.75-1, and I am running
redhat-config-printer-0.6.79.5-1. Either the patch fell off, or it
was reversed, or they changed XP in a way that makes samba break or
I have also read through the errata. It could have been more specific,
I guess I believe that when no userid or password is needed by the
system for printing, that none need be specified. Looking at the man
page for smbspool makes it clear that it is legitimate to *not*
specify a userid or password in the URL.
Finally, any userid works equally well. I reconfigured the printer to
use the userid zithead (which does not and never has existed on the
gateway system and also has no special meanings in contexts other than
the teenage acne sort), and the result was just as excellent as when I
used the userid guest.
[njs@quickdraw njs]$ rpm -q redhat-config-printer
You have new mail in /var/spool/mail/njs
[njs@quickdraw njs]$ rpm -q cups
You have new mail in /var/spool/mail/njs
[njs@quickdraw njs]$ rpm -q samba
To me, this makes it clear that the bug is in samba, and not in
redhat-config-printer and CUPS. I did find some bugs when I was doing
my research which indicated that different things might be done when a
userid was vs. was not specified on a command.
Then I found 104136.
This is probably an actual duplicate of that. If you agree, close it
as a dup.
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.
*** This bug has been marked as a duplicate of 104136 ***