Many RDP sessions will not start
I have recently installed RDM on my Ubuntu 20.04 machine using X11.
At first, my problem was connecting to an MS SQL server using AD credentials.
I've given up on that, and just created a SQL account for meself and it ended up being a dbowner, before I could finally connect.
The connection is there and I see all the trees and servers defined and the look and feel seems ok as well.
Then I wanted to open a RDP session, which is mostly what I'm going to use it for.
But when double-clicking a VM, or just choosing Open Session, the screen (VM pane in RDM) goes black for a second or so and then it just exits.
No message, no error.
Connections.log shows:
[12/16/2020 5:45:44 PM] Connecting - 'MyVM001' (RDP (Microsoft Remote Desktop)) [12/16/2020 5:46:16 PM] Viewed entry - 'MyVM001' (RDP (Microsoft Remote Desktop)) [12/16/2020 5:53:00 PM] Information - 'MyVM001': Inherits credential from Parent [12/16/2020 5:53:00 PM] Information - 'Pleasant Password': Used by 'TestVMs' [Session] [12/16/2020 5:53:01 PM] Connecting - 'MyVM002' (RDP (Microsoft Remote Desktop)) [12/16/2020 5:53:02 PM] Disconnected - 'MyVM002' (RDP (Microsoft Remote Desktop)) [12/16/2020 5:55:36 PM] Connecting - 'MyVM003' (RDP (Microsoft Remote Desktop)) [12/16/2020 5:55:44 PM] Viewed entry - 'MyVM003' (RDP (Microsoft Remote Desktop)) [12/16/2020 5:56:10 PM] Connecting - 'MyVM004' (RDP (Microsoft Remote Desktop)) [12/16/2020 5:56:11 PM] Disconnected - 'MyVM004' (RDP (Microsoft Remote Desktop)) [12/16/2020 6:00:49 PM] Disconnected - 'MyVM003' (RDP (Microsoft Remote Desktop)) [12/16/2020 6:01:29 PM] Disconnected - 'MyVM001' (RDP (Microsoft Remote Desktop))
The RemoteDesktopManager.log doesn't get any extra lines during a connection.
The VM's MyVM001 and MyVM003 work, but MyVM002 and MyVM004 disconnect straight away.
So there is a way that it can work, but I don't see the difference between the VM's.
We have most credentials set up with a Pleasant Password Server integration, but even hosts that do not have credentials filled in don't work.
The 'view password' bit does work on hosts with Pleasant Password Server configured, so I guess that bit works.
We have thousands of servers, and I found a group of about 5 that work. These are all Windows 2019. Some connect through a DNS record, others through IP.
I also found Windows 2019 servers that don't work though, so I don't think it's OS related.
I tried some of the hosts that do not work and just 'rdesktop <hostname>' and that works fine, after a unknown certificate warning.
Is there anything else I can try to get this working?
I was very happy to find out there is finally a Linux port for RDM, which was the only reason for not using Linux at work.
So if I would get this to work, it would make my life a lot easier.
All Comments (11)
Hi,
Indeed, AD login are not yet supported in RDM Linux. This is a limitation of the mono platform.
There was recently development on this and we are hopeful this will be available soon in RDM.
The RDP module ouputs logs in the console.
You can run RDM in a terminal using the 'remotedesktopmanager' command.
That should give us more information to work with.
Regards
Jonathan Lafontaine
This is what it says when I connect to a host, that doesn't work
$ remotedesktopmanager 45171 4r8pBjgFhkqwByC-6T-d0w ================================================================= Native Crash Reporting ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. =================================================================
This is the log when I succesfully connect:
$ remotedesktopmanager 36405 XOuxgfdYRkKrO4MUOXdHvw [18:58:28:646] [75669:75673] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [18:58:28:646] [75669:75673] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [18:58:28:646] [75669:75673] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [18:58:28:357] [75669:75673] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized calling freerdp_InitializeSSL freerdp_InitializeSSL #1 freerdp_InitializeSSL #2 ___freerdp_openssl_initialize #1 ___freerdp_openssl_initialize #2 OPENSSL_VERSION_NUMBER: 0x1010104F ___freerdp_openssl_initialize #4 ___freerdp_openssl_initialize #5 [18:58:28:373] [75669:75673] [INFO][com.freerdp.core] - freerdp_set_last_error resetting error state [18:58:28:385] [75669:75673] [INFO][com.freerdp.core] - freerdp_set_last_error resetting error state [18:58:38:846] [75669:75673] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [18:58:38:846] [75669:75673] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [18:58:38:846] [75669:75673] [INFO][com.freerdp.channels.rdpsnd.client] - Loaded fake backend for rdpsnd [18:58:38:846] [75669:75673] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [18:58:38:382] [75669:75737] [WARN][com.freerdp.channels.cliprdr.common] - [cliprdr_packet_format_list_new] called with invalid type 00000000
The successful one shows even more errors :D (j/k, I know they're info)
As a test, could you disable clipboard support on one of the failing session?
You can disable the clipboard in the Local Devices and Resources tab of the RDP entry settings.
Jonathan Lafontaine
Good call, that seems to make it work! :)
Allthough I tried a different server (Windows 2008 R2), but that still didn't work after turning the Clipboard off.
The ones that already worked before also had Clipboard turned on as well.
So we're not quite there yet.
By the way, thanks for the quick response :)
We'll get there :)
Do the 2008 R2 server crashes like the other one with the same output?
Jonathan Lafontaine
Yes, it does.
And I also found other Windows 2019 ones that still don't do anything after turning the Clipboard off.
These two actually start working when I turn Credentials from Inherited to Default.
Inherited means they are passed to a credential inside the Pleasant Password Server.
I think my local DB account doesn't have permissions there, won't get authenticated.
But on the first server I tried the Clipboard setting on, I actually got a Pleasant Password Server popup.
On the last two, both Windows 2008R2 and Windows 2019 (coincidently at the same customer) I didn't have to turn Clipboard off, I just had to change the credential.
I don't really see any other output, except for a bunch of Gtk-CRITICAL ones about 'text !- NULL' when I open the properties.
Are you able to 'view password' on the failing connection?
I recently implemented missing settings window for Pleasant Password Server.
I'm wondering if that could be what's causing problem.
Jonathan Lafontaine
I can view the credentials using the 'View Password' option on all the hosts.
But it looks valid that this has something to do with it.
On a side-note, RDM sometimes crashes when editting the properties of a host.
In this case:
================================================================= Native Crash Reporting ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ================================================================= Native stacktrace: ================================================================= 0x5593db286229 - ./RemoteDesktopManager : 0x5593db2865a9 - ./RemoteDesktopManager : 0x5593db2327c4 - ./RemoteDesktopManager : 0x5593db27fbe5 - ./RemoteDesktopManager : 0x7fefde8af028 - /lib/x86_64-linux-gnu/libglib-2.0.so.0 : 0x5593e5496090 - Unknown ================================================================= Telemetry Dumper: ================================================================= Pkilling 0x140667926066944x from 0x140668349530048x Pkilling 0x140667921864448x from 0x140668349530048x Pkilling 0x140665298085632x from 0x140668349530048x Pkilling 0x140665293883136x from 0x140668349530048x Pkilling 0x140665289680640x from 0x140668349530048x Pkilling 0x140665285478144x from 0x140668349530048x Pkilling 0x140666173638400x from 0x140668349530048x Pkilling 0x140666166212352x from 0x140668349530048x Pkilling 0x140666162009856x from 0x140668349530048x Pkilling 0x140666158331648x from 0x140668349530048x Pkilling 0x140668256581376x from 0x140668349530048x Pkilling 0x140665679165184x from 0x140668349530048x Pkilling 0x140665310672640x from 0x140668349530048x Pkilling 0x140667923965696x from 0x140668349530048x Pkilling 0x140665291781888x from 0x140668349530048x Pkilling 0x140665287579392x from 0x140668349530048x Pkilling 0x140664843007744x from 0x140668349530048x Pkilling 0x140667919746816x from 0x140668349530048x Pkilling 0x140667461302016x from 0x140668349530048x Pkilling 0x140666164111104x from 0x140668349530048x Pkilling 0x140665306478336x from 0x140668349530048x Entering thread summarizer pause from 0x140668349530048x Finished thread summarizer pause from 0x140668349530048x. Failed to create breadcrumb file (null)/crash_hash_0xdde48c5c5 Waiting for dumping threads to resume ================================================================= External Debugger Dump: ================================================================= mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb ================================================================= Basic Fault Address Reporting ================================================================= Memory around native instruction pointer (0x7fefde8af028):0x7fefde8af018 85 c0 74 03 44 8b 00 48 8b 47 08 48 85 c0 74 12 ..t.D..H.G.H..t. 0x7fefde8af028 48 39 78 18 74 12 48 89 c7 48 8b 47 08 48 85 c0 H9x.t.H..H.G.H.. 0x7fefde8af038 75 ee 44 89 c0 c3 66 90 48 8b 48 10 ba 01 00 00 u.D...f.H.H..... 0x7fefde8af048 00 48 85 c9 74 05 8b 11 83 c2 01 41 01 d0 eb d6 .H..t......A.... ================================================================= Managed Stacktrace: ================================================================= at <unknown> <0xffffffff> at System.Object:wrapper_native_0x7fefdf3bb430 <0x0008b> at Gtk.TreeStore:Clear <0x0003f> at Client.Views.Controls.ConnectionTreeView:ClearConnectionTree <0x000f3> at Client.Views.Controls.ConnectionTreeView:LoadConnectionList <0x0010f> at Client.Windows.MainWindow:LoadAllConnectionView <0x0005b> at Client.Windows.MainWindow:RefreshAllConnectionView <0x0004f> at Client.Windows.MainWindow:RefreshViewBase <0x00097> at Client.Windows.MainWindow:RefreshView <0x00033> at Devolutions.RemoteDesktopManager.Managers.ActionManager:EditConnection <0x00b4b> at <>c:<get_PropertiesState>b__182_2 <0x00067> at Client.Views.Controls.ActionButton:<set_ActionState>b__5_1 <0x00069> at <Module>:runtime_invoke_void__this___object_object <0x000a0> at <unknown> <0xffffffff> at System.Reflection.RuntimeMethodInfo:InternalInvoke <0x000ad> at System.Reflection.RuntimeMethodInfo:Invoke <0x00123> at System.Reflection.MethodBase:Invoke <0x00049> at System.Delegate:DynamicInvokeImpl <0x002b7> at System.MulticastDelegate:DynamicInvokeImpl <0x0004f> at System.Delegate:DynamicInvoke <0x00038> at GLib.Signal:ClosureInvokedCB <0x000bf> at GLib.SignalClosure:Invoke <0x00047> at GLib.SignalClosure:MarshalCallback <0x002d3> at GLib.SignalClosure:MarshalCallback <0x00087> at <unknown> <0xffffffff> at System.Object:wrapper_native_0x7fefdf29c300 <0x00088> at Gtk.Application:Run <0x00032> at Devolutions.RemoteDesktopManager.Program:Main <0x00073> at <Module>:runtime_invoke_void_object <0x00091> ================================================================= /usr/bin/remotedesktopmanager: line 4: 95793 Aborted ./RemoteDesktopManager
Are you able to spot a pattern that would lead to a crash?
By the looks of it, GTK really doesn't like having it's data store cleared but I've never experienced that particular crash.
I'll have to figure out what's different on your setup.
Jonathan Lafontaine
Well, on one server I keep changing Credentials back and forth from Inherited to Default and it crashes both ways. But does save the change.
On other servers I didn't get that, so far.
I also noticed that sometimes on logoff, it just freezes. And the other tabs are un responsive as well.
The console shows the following error.
[19:49:31:389] [92152:92405] [INFO][com.freerdp.core] - ERRINFO_LOGOFF_BY_USER (0x0000000C):The disconnection was initiated by the user logging off their session on the server. ERROR SILENT: Disconnected from remote host.
But those are all different problems. We were still on the Credential thing :D
I just tried "Open with Parameters" -> "Open (Select Credentials)".
I actually get to choose the Pleasant Password Server and scroll to the correct credential. And then it just closes with the before mentioned Native Crash Reporting error.
So it's not really like it can't get to the information.
Hi there
Just a quick note to say that I had the exact same issue with Ubuntu 20.04 newly installed and RDM 2020.3.1. Data source is a Devolution Online Drive.
I had to recreate the credentials entry and change it from LastPass (there seems to be a bug in this type of credential entry too but that's not for this thread) to a username/password credential entry. Once changed in the RDP settings, I was able to login to the Windows Servers (2016, 2019).
I agree with Stephan though as it looks to be a credential source issue.
Just my 2 cents.