Login dialog from Tumbleweed recjected, from Mac or from Windows user and PW are ok

Hi!

Strange thing. Until recently I was able to log into a remote windows server using openvpn and into a local mac os x server using dolphin: For the latter I wrote into the address line

smb:/USER:PASSWORD@IP-of-server

Then a frame appears and asks again for USER and PASSWORD, but always simply reappears without the password.

openvpn: “openvpn --config name-of-config-file.ovpn”. I can log in, but when I open Dolphin, I’m asked again to provide USER and PASSWORD and after providing them, the frame just reappears without the password.

So probably there is something wrong with the way, KDE handels the access.

From other computers here in the LAN I can access the local server and from my office PC the remote server. So the error has to be on this machine with Tumbleweed on it. Any ideas?

Are you sure you’re not doing a “double whack” (smb://) instead of a single whack?

As for your Dolphin situation, you will need to post <exactly> the commands you’re using (perhaps sanitized with dummy username/passwords). If you are changing how the machine is identified in any way, then you will need to re-issue your credentials.

If you want to avoid simple mistakes, convert all your commonly used commands into scripts so that they’re always executed the same way no matter your recollection or possible finger-fehlers (a chess term for touching things inadvertently like typing mistakes).

TSU

On the command line, everything works.

smbclient -L //192.168.1.25/

asks for the password of the User “XY”. As “XY” is the username on the Client as well as on the server, that’s ok.

I get the shares and can start an smbclient shell:

smbclient //192.168.1.25/Share

Password asked and then I’m getting the prompt “smb: >”. I can run “ls” and whatever.

But if I’m using (like always before!) dolphin, it doesn’t. I’m clicking on network, smb-shares and then type into the address line of dolphing:

smb:/XY:Password@192.168.1.25/Share

Result: either “access denied” or I get the authentication dialog forever.

Perhaps I wasn’t clear…
Try your SMB connection commaind as follows

smb://XY:Password@192.168.1.25/Share

TSU

Thank you, but I’ve been trying this as well. Same result. I’ll ask on the factory mailing list.

Immediately after you try the command and it fails, try grabbing the last 20 journal entries with the following immediately

journalctl -n 20

Also, try connecting with just the Username (You should be prompted to enter the password only)

smb://XY@192.168.1.25/Share

And try again without any credentials (You should be prompted to enter both Username, then Password)

smb://192.168.1.25/Share

Somewhere in the above 3 tries, you should be able to narrow down exactly which part of the command isn’t working

TSU

Whatever I do, I’m always getting the same result: the authentication windows reappears.

From the journal:

Apr 22 19:17:25 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: Widget for 146800645 QWidget(0x0)
Apr 22 19:17:25 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: Showing password dialog KPasswordDialog(0xf0d130, name="KPasswordDialog") , window-id= 146800645
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: dialog result= 1 , bypassCacheAndKWallet? false
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1" window-id= 146800645 username= "XY" realm= "" seqNr= 61 keepPassword? true canceled? false
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1" expire= 1 window-id= 146800645 keep= true
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1"
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: User = "XY" , Realm = "" , WindowId = 146800645
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: walletKey = "smb-192.168.1.25:-1"   reading existing map
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: writing to  "login" , "password"
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1" window-id= 146800645 username= "XY" realm= "" seqNr= 62 keepPassword? false canceled? false
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1" expire= 1 window-id= 146800645 keep= false
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: User = "XY" , WindowId = 146800645 seqNr = 61 , errorMsg = ""
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1" , user= "XY" seqNr: request= 61 , result= 62
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: auto retry!
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1" expire= 1 window-id= 146800645 keep= false
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1"
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: User = "XY" , WindowId = 146800645 seqNr = 62 , errorMsg = ""
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: key= "smb-192.168.1.25:-1" , user= "XY" seqNr: request= 62 , result= 62
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: Widget for 146800645 QWidget(0x0)
Apr 22 19:17:26 linux-k2bd.site org.kde.kpasswdserver[1910]: org.kde.kio.kpasswdserver: Showing password dialog KPasswordDialog(0xd8a080, name="KPasswordDialog") , window-id= 146800645

From commandline, I can easily get a connection:

smbclient -L //192.168.1.25

lists the shares, e.g.

My guess is that you have incorrect (old, expired, changed?) creentials in kwallet, so you need to clear that entry so a new value will be stored.

That’s a bit of a guess because of the system re-trying multiple times… You may need to increase the number of journal entries retrieved to view the first lines relevant to your problem.

TSU

No, nothing. Thank you again.

I tried as root as well (Dolphin in superuser mode), without succes. Neither Dolphin opens the share of the openvpn connection, nor to the smb-connection to the local server.