-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server example: [failed to negotiate security protocol] general error #652
Comments
The server uses "user"/"pass" as username and password by default. This mode is quite insecure, and thus not really well supported. Furthermore, it's not clear how to indicate to the client wrong credentials, and right now the connection is simply closed. We may want to explore other options, better defaults, though. |
I did login with "user"/"pass" so I don't think the problem was caused by wrong credentials. Is there a known working configuration for the server example? Here is a more complete trace of what happens when connecting with the default username and password:
|
It works on fc41(remmina-1.4.35-3.fc41.x86_64), and freerdp git. What version are you using? Maybe you could try enabling the client log? |
Ok, now we have something to work with! This is the output from running in the terminal which shows the errors from freerdp.
Following the instructions in openssl/openssl#21247 (comment), I am able to re-enable the md4 cipher, however I still have these last couple errors:
Remmina version: 1.4.39 (git n/a) |
On the server side, I also see very similar errors when connecting from the Windows 11 RDP client:
The error on the Window client side is:
|
@elmarco were you able to reproduce this issue with either Remina (1.4.39 with librdpfree 3.10.3) or the Windows 11 RDP client? |
Testing the server example from the latest release ironrdp-v0.7.3 against Remmina Remote Desktop Client (libfreerdp 3.10.3), I keep running into these errors while trying to connect:
In Remmina, I set the host to 127.0.0.1 and leave the username/password at their default settings. In addition to these messages, the client fails to connect.
The text was updated successfully, but these errors were encountered: