Bug 229448

Summary: Dolphin cannot authenticate smb shares
Product: [Frameworks and Libraries] kio Reporter: Doug Roberts <doug>
Component: smbAssignee: David Faure <faure>
Status: RESOLVED DUPLICATE    
Severity: normal CC: doug, eur36, jkoelndorfer, nate
Priority: NOR    
Version: 4.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Doug Roberts 2010-03-04 21:41:26 UTC 
Version:           1.4 (using KDE 4.4.1)
Compiler:          4.4.1 
OS:                Linux
Installed from:    Ubuntu Packages

When you supply an smb url to dolphin, an authentication window pops up.  Enter username and password, click "ok", and it does not authenticate; the authentication window just keeps popping back up.

It is impossible to access smb shares with the current 4.4.1 version of dolphin.  It used to work in KDE 3.5.

Running Kubuntu 9.10, KDE 4.4.1 (ppa), Dolphin 1.4, AMD X86_64.
Comment 1 Doug Roberts 2010-03-04 21:43:54 UTC 
Konqueror 4.4.1 exhibits the same behavior, BTW.
Comment 2 John Koelndorfer 2010-10-05 18:52:52 UTC 
I can confirm this issue in KDE 4.5.1 (using Arch Linux). However, you can work around the issue by making sure the SMB URI contains the username: i.e.

"smb://user@server/sharename" works, but

"smb://server/sharename" DOES NOT work (even if you correctly enter the username in the dialog box). In remote:/ you can fix your URIs to include the username you want to connect as and things should work. Annoying, though.
Comment 3 europe 2010-12-05 17:09:55 UTC 
I can confirm this issue using KDE 4.5.1 (Kubuntu 10.10). Even if I enter the password in the authentication window no connection will be established. The smb server message is: 
smbd/password.c:authorise_login(865)
authorise_login: rejected invalid user nobody
Via "create new link to address" and entering the address like mentioned from John Koelndorfer a dolphin error message appears like "writing not possible".
Very annoying!
Comment 4 Nate Graham 2017-10-28 17:12:51 UTC 

*** This bug has been marked as a duplicate of bug 209431 ***