RDM Jump 2026.1.10.0 does not work

Hello

That's really strange. What specific version of RDM do you have? It it at least 2026.1.9 (I want to understand you're not using an earlier beta). What kind of data source do you use?

In terms of getting things unblocked for you right now, do you have more than one jump host? On the client-side RDM, on the Jump setting page for the Jump Host RDP connection please try changing the "Jump Approach" to "Legacy". Please try it on at least one Jump Host and let me know if it unblocks things for you.

And let me know if something isn't clear or you have another question

Thanks and kind regards

Hi Richard

Alex has posted more than me (a new post).. But I did the same... concerning your questions, I will do my best to fullfill them asap, hopefully on Monday.

cheers
Matthias

Hi Richard

Alex has posted more than me (a new post).. But I did the same... concerning your questions, I will do my best to fullfill them asap, hopefully on Monday.

cheers
Matthias

@matthiasgruber
I Downgraded jump host to 2025 version an it works again. waiting for new releases

Hello

That's really strange. What specific version of RDM do you have? It it at least 2026.1.9 (I want to understand you're not using an earlier beta). What kind of data source do you use?

In terms of getting things unblocked for you right now, do you have more than one jump host? On the client-side RDM, on the Jump setting page for the Jump Host RDP connection please try changing the "Jump Approach" to "Legacy". Please try it on at least one Jump Host and let me know if it unblocks things for you.

And let me know if something isn't clear or you have another question

Thanks and kind regards

@Richard Markiewicz
Hi Richard,

Argh... just lost my Reply-Window... okay propably better, that the shorter Reply with lover prose-Level :-), because running out of spare-time :-)

• Data Source - XML Local
• Upgrade from 2025.3.32.0 no Beta, never ever...unfortunately not the time for that.
• RDM runns on both Machines (Jumpserver and my Workstation) as "Portable" (has to be), you know, this override.cfg - Version
• Tried the Legacy, I think its Properties (for the jumpserver) -> Jump -> Is Jump host -> Legacy restarted everything (RDM; Jumptool etc.) nop.. neither a SSH-Jump nor a RDP-Jump works

I gave it a try Client 2025.3.32.0 -> Jump Host 2026.1.10.0 this is working, seems you have some trouble with 2026.1 -> 2026.1 (on 2025.3. is no Legacy-Switch ;-))

Normally I would check it with some wireshark to see what traffic is running, if there is some sort of handshake, but running out of time for Debugging... I give it a try later the day...
As Alex mentioned, rollback all to 2025.3 and there is not a problem... what is not suppring :-)


Since we have two Posts with the same trouble, perhaps its possible to join them?

cheers
Matthias

Hello

That's really strange. What specific version of RDM do you have? It it at least 2026.1.9 (I want to understand you're not using an earlier beta). What kind of data source do you use?

In terms of getting things unblocked for you right now, do you have more than one jump host? On the client-side RDM, on the Jump setting page for the Jump Host RDP connection please try changing the "Jump Approach" to "Legacy". Please try it on at least one Jump Host and let me know if it unblocks things for you.

And let me know if something isn't clear or you have another question

Thanks and kind regards

@Richard Markiewicz
Hi Richard,

Argh... just lost my Reply-Window... okay propably better, that the shorter Reply with lover prose-Level :-), because running out of spare-time :-)

• Data Source - XML Local
• Upgrade from 2025.3.32.0 no Beta, never ever...unfortunately not the time for that.
• RDM runns on both Machines (Jumpserver and my Workstation) as "Portable" (has to be), you know, this override.cfg - Version
• Tried the Legacy, I think its Properties (for the jumpserver) -> Jump -> Is Jump host -> Legacy restarted everything (RDM; Jumptool etc.) nop.. neither a SSH-Jump nor a RDP-Jump works

I gave it a try Client 2025.3.32.0 -> Jump Host 2026.1.10.0 this is working, seems you have some trouble with 2026.1 -> 2026.1 (on 2025.3. is no Legacy-Switch ;-))

Normally I would check it with some wireshark to see what traffic is running, if there is some sort of handshake, but running out of time for Debugging... I give it a try later the day...
As Alex mentioned, rollback all to 2025.3 and there is not a problem... what is not suppring :-)


Since we have two Posts with the same trouble, perhaps its possible to join them?

cheers
Matthias

@matthiasgruber
Hi Matthias,

in my topic Devolutions mentioned that this is a known issue atm and a Fix is on its way.

Hello

Yes, as Alex wrote this should be fixed in 2026.1.11 (should be released soon).

Sorry again for the inconvenience

Thanks and kind regards,