Beta v2024.1.11.0 - Hangs when disconnecting RDP Session of the main Jump Host
Beta v2024.1.11.0 - Hangs when disconnecting RDP Session of the main Jump Host
Good morning.
One thing I have noticed since updating to Beta last week, is when normally disconnecting from an RDP session like I normally do (closing the tab), it now freezes and hangs.
This is the configuration I have used with no issues:
I have searched the InterTwebs and found the following articles which I incorporated:
https://blog.devolutions.net/2014/12/rdm-hangs-when-logging-off-rdp-sessions/
https://docs.devolutions.net/kb/remote-desktop-manager/troubleshooting-articles/microsoft-rdp-logoff-issue/
When disconnecting from any RDP session that is NOT set as "Is Jump Host" on the entry, the Profiler Debug shows the following. Green is on connection, Yellow is on disconnect.
As you can see, I have also gone in per one of the articles and disabled the UDP Transport:
Only thing that is different with the servers having the issue, versus servers not having the issue is the Jump Server obviously have RDM Agent installed:
The two Jump Servers are production, so they have the latest RDM Stable Release on them, where my laptop has the latest Beta version for testing purposes and daily usage.
Thanks!
--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM
f70487ad-5cca-416c-ba08-990450729122.png
3ccc6a41-39a8-4900-9339-c19cf3bff37c.png
b877e35e-e939-40f4-9201-41ae6654e64d.png
4e92ed7f-42ee-4ed2-b674-c74ac00ee989.png
c2754259-09bd-4d9c-87a5-76099d2d7dc8.png
8f5fab73-26a1-4f49-9586-62a263d3390b.png
b853355a-c7a2-4750-9417-f199866fa9a7.png
All Comments (5)
Hi Chuck,
This is most likely due to having RDM & RDMAgent versions out of sync, client vs jump host.
v2024.1 has been updated to use .NET 8.0, instead of .NET Framework 4.8 and, from what we've been able to gather over the last few weeks, the jump messages don't properly convert when you have a .NET mismatch.
As you mentioned, both jump hosts are production machines. Do you have a non-production machine you could test on? Installing the latest beta should resolve the issue.
Best regards,
Stéfane Lavergne
Hi Chuck,
This is most likely due to having RDM & RDMAgent versions out of sync, client vs jump host.
v2024.1 has been updated to use .NET 8.0, instead of .NET Framework 4.8 and, from what we've been able to gather over the last few weeks, the jump messages don't properly convert when you have a .NET mismatch.
As you mentioned, both jump hosts are production machines. Do you have a non-production machine you could test on? Installing the latest beta should resolve the issue.
Best regards,
Thank you, sir. I do have a server I can do some sort of testing on.
Would you be able to send me a DM with a direct link for the Beta download so I don't have to download the main version then upgrade?
Thank you.
--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM
Here are the current beta URLs
Download:
- https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2024.1.11.0.exe
- https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.2024.1.11.0.zip
More info:
https://forum.devolutions.net/topics/41137/remote-desktop-manager-20241--beta#186956
Stéfane Lavergne
Sir:
I updated RDM this morning with the new Stable release that was published.
The hanging when logging off a Jump server no longer exists, so the new version has fixed that issue.
Also, you are correct. It is because the versions are/were out of sync.
I updated mine this morning and left another jump server on an older version, and the instructions that the jump server needs to do did not function.
Upon updating the jump server RDM and Agent versions, it works as expected.
Thanks for the assistance!
--- Chuck
Overgaard, AZ (-7 MST / Zulu Year-Round)
RDM Version: 2025.3.11.0 64-Bit - MSSQL - Daily Usage
RDM Version: 2025.2.28.0 64-Bit - MSSQL - VM
Thank you for the update.
Best regards,
Stéfane Lavergne