Linux RDM client 'closes RDP connections' when using any other credential option than Devolutions password server
Linux RDM client 'closes RDP connections' when using any other credential option than Devolutions password server
Hi,
We are test deploying remote desktop manager client for Linux at
the moment. We are using RDM Enterprise Edition.
Ubuntu Linux to be precise.
However, I have noticed the Linux client instantly closes
connections that use any other credential option than our company-hosted Devolutions
password server.
This is an issue, because it is not the expected nor desired
behavior. Expected would be at least an error before closing the connection to
the entry.
Desired would be that the Linux client copies the WIndows' client behavior in this regard, namely offering a credential enter window where it
waits for credential (username + password) input to connect to the RDP server.
This has so far only been observed for RDP sessions, which we use heavily in
our company.
Connecting to Windows terminal servers also does not work, because
terminal servers by default we always prompt for credentials, as we want
multiple users to be able to connect to those at once.
All Comments (7)
I'm don't work for Devolutions, but just wanted to say 2 things.
1) That behavior is probably not implemented yet. The Linux client is still in beta and actively (aggressively even) developed adding features every release.
2) Regarding "... we always prompt for credentials, as we want multiple users to be able to connect to those at once.". That's a perfect use case for user vault (https://help.remotedesktopmanager.com/view_navigation_privatevault.html )entries and then referencing those entries from your host entry. Something to look into.
Hi
Can you give me a bit more info about your RDP and credential entry settings when it fails to connect?
RDP session do have prompt for credentials.
That being said we have to keep in mind RDM Linux uses a library called FreeRDP to establish rdp session.
It might not behave exactly like the official Microsoft ActiveX that RDM Windows uses.
If you wish to test this more on your end, you can switch to FreeRDP in RDM Windows in the RDP entry advanced tab.
Nevertheless, I will test different prompt for credentials scenario to see how the application behave.
Regards
Jonathan Lafontaine
Alright, RDP type is "normal" without any credentials filled in. On the General tab, the display is set to embedded (tabbed) and credentials is set to none.
The rest of the settings seem to be default (connection verification is on and TLS is enabled)
The connection just quickly opens and immediately closes without any error message as soon as Connect is pressed or when the entry is double-clicked.
Any connection where the credentials are set to Credential repository, do work.
I'm don't work for Devolutions, but just wanted to say 2 things.
1) That behavior is probably not implemented yet. The Linux client is still in beta and actively (aggressively even) developed adding features every release.
2) Regarding "... we always prompt for credentials, as we want multiple users to be able to connect to those at once.". That's a perfect use case for user vault (https://help.remotedesktopmanager.com/view_navigation_privatevault.html )entries and then referencing those entries from your host entry. Something to look into.
Thanks for the hint, will look into user vault
Could you try settings Credentials to "Default" in the General Tab?
Jonathan Lafontaine
Did it, but did not make any difference, even after restarting RDM. The client still closes the RDP window immediately. Maybe I am missing some packages?
You can run the "remotedesktopmanager" command in a terminal.
The output might help us a bit.
Jonathan Lafontaine