Bug 146980

Summary:	NT_ACCESS_DENIED error when installing a samba printer
Product:	[Unmaintained] kdeprint	Reporter:	Arnout Boelens <a.m.p.boelens>
Component:	general	Assignee:	KDEPrint Devel Mailinglist <kde-print-devel>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	jlayt
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Arnout Boelens 2007-06-19 22:15:48 UTC

Version:            (using KDE KDE 3.5.7)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I hit some weird behaviour when trying to install a samba printer using the print wizard. I had to follow this procedure to install my printer (from http://www.mepis.org/node/3458):

Here's what worked for me.
- Log into the Printer wizard as Administrator.
- When you launch the Add printer wizard, choose SMB shared printer.
- In the next screen(user identification), choose Anonymous(no login/no password)
- Proceed to the next screen, and SCAN your network.(This is where you will get the NT_ACCESS_DENIED message if you try to access your Windows network)
- Now Don't touch anything, and go BACK one step to the previous screen (User identification).
- In the user identification screen, choose guest(login = "guest").
- Proceed to the next screen. DO NOT repeat a scan. Just try to access your Windows network in the displayed tree. You should magically see your Windows printer appear without any whining about access.

When I try to scan the network as a guest, I am not able to see which computers belong to the various workgroups.

Cheers,

Arnout

Comment 1 Kurt Pfeifle 2007-06-20 23:00:55 UTC

And how is this a bug? And why a bug that should be reported against KDEPrint??

What happens is this: you are trying to anonymously access a Windows resource that is not accessible for anonymous users. You get "access denied" (rightly so).

Next you try to access the same resource, this time not anonymously (user "guest" is a valid account) and you get in.

(And you do not need to repeat the scan because the wizard cached the results of the last scan and still displays them).

The same will happen, if you used the "smbclient" commandline utility, once with the "-U%" parameter (no loginname, no password), and once with "-Uguest%" ("guest" loginname, no password), and once with "-Uguest%secret" ("guest" loginname, password used: "secret"), depending on wether your Windows allows empty passwords for guest or not.

Can you elaborate on why this should be regarded as a bug of KDEPrint? (Otherwise I'll close this report.)

Thanks.

Comment 2 Arnout Boelens 2007-06-20 23:40:17 UTC

I think this is a kdeprint bug because I am using the kdeprint wizard to add a printer and it doesn't work as expected. What I would expect, is that I can always scan the whole network and then get an access denied error when I actually try to access a server with the wrong authentication. Right now the following happens: I can only scan the network and find the server I want to connect to, being an anonymous user, but I can only connect to this server as a guest. As a result I have to follow the procedure above. 

Would it work if the network scan is alway perform as an anonymous user and that the login info (anonymous, guest or username) is only used when accessing a server?

Comment 3 Kurt Pfeifle 2007-06-21 19:11:24 UTC

Let me understand you right: are you saying that the *scanning* itself does only work as anonymous user, but does not work as user "guest"? And that therefor you first need to scan anonymously?

Comment 4 Arnout Boelens 2007-06-21 19:35:51 UTC

Yes, that is correct.

Comment 5 John Layt 2011-05-27 18:34:15 UTC

KDEPrint is obsolete, unmaintained and will never be revived.  Closing all open bugs.