I wasn't able to connect to a Windows 8 machine using krdc. It would just display a blank screen, with no messages. (Same as when the server is not responding, or DNS name does not resolve, etc.) After trying to connect using rdesktop, I discovered that the Windows machine was working fine - but it wanted me to change the password. When I did, krdc started working again. Reproducible: Always
KRDC from KDE SC 4.11 uses xfreerdp for RDP support. Please try to reproduce it with xfreerdp. If you can reproduce it, please report it there and post a link here.
I've reproduced the problem; it's caused by network level authentication: https://github.com/FreeRDP/FreeRDP/issues/1510 This fails: $ xfreerdp -u [username] [hostname] connected to [hostname]:3389 Password: SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. This works: $ xfreerdp --no-nla -u [username] [hostname] connected to [hostname]:3389
(In reply to comment #2) > I've reproduced the problem; it's caused by network level authentication: > https://github.com/FreeRDP/FreeRDP/issues/1510 > > This fails: > > $ xfreerdp -u [username] [hostname] > connected to [hostname]:3389 > Password: SSL_read: Failure in SSL library (protocol error?) > Authentication failure, check credentials. > If credentials are valid, the NTLMSSP implementation may be to blame. > > This works: > > $ xfreerdp --no-nla -u [username] [hostname] > connected to [hostname]:3389 So you think we should pass "--no-nla" by default?
(Sorry, it's been a while, but the password has expired again, so the error message is back.) I would assume that "--no-nla" will cause the server to always prompt the user to enter the password, even if it's already entered in krdc. One option would be to try the normal way first, and if that fails, then try "--no-nla".
Created attachment 97001 [details] Detect the connection failure and leave the rdp window Read the return message from xfreerdp to check if the connection fails, and then return to the main window.
This one has always complicated my work with krdc! Even though detecting the failure and returning at least some message helps, I don't think it's the right solution. Isn't it possible to get user to login screen so he can see what's happening while keeping the possibility of storing credentials? Because even if you get error, you'll still need to open console, create a RDP connection manually, get the credentials from wallet, change the password and then store it. Doesn't happen that often, but it's major pain.
Hi Matej, Could you explain your issue more detail? Are you saying that the password doesn't match to the one stored in kwallet? And you want to prompt a dialog to enter and store the new password if login failed?