Swapped from Windows to Linux RDM is failing RDP w/RD Gateway based Jumpbox

Swapped from Windows to Linux RDM is failing RDP w/RD Gateway based Jumpbox

avatar
fpantovich

I swapped from a Windows based work laptop to a Linux based one finally. Tried to do the whole export/import configuration side of things and that failed due to the Microsoft RD Gateway being used inherently on the Windows side and not be a supported function, naturally, on the Linux side.

I tested with xfreerdp3 in CLI and found that in order to have the whole Windows Jumpbox (RD Gateway) AND Windows endpoint RDP to work I have to have these flags in the xfreerdp3 command and I cannot figure out how to get it to work on the Devolutions RDM side of things.

"/auth-pkg-list:\!u2u /cert:ignore"

Tried searching and even using AI to figure this out, but apparently the Linux distro for this is pretty minimal at best on the documentation availability that AI can reach, so not very helpful unfortunately other than figuring out the root case.

Any advice to resolve this?

I tried recreating the jumpboxes as specific IsJumpbox =$true but that didn't work. I then also tried the RD Gateway tab and enabled/disabled a ton of settings and that was a no go. I was going to try using an external client (xfreerdp3) in the global settings, but I can't seem to find all the variables appropriate for seeding in the gateway specific items for some reason.

Looking for any advice to get me moving in the right direction here so I can continue using Devolutions RDM, please. Thanks.

All Comments (1)

avatar
Richard Markiewicz

Hello

I think the best thing to do, is get it worked with the embedded RDP in RDM; and then if you want to use xfreerdp3 in external mode, you'll know you have the good settings and it's just a case of mapping them to the CLI.

I'm afraid I'm not sure what you mean by

I tried recreating the jumpboxes as specific IsJumpbox =$true but that didn't work


However, I was using an RD Gateway connection from RDM Linux just the other day and found it to work well - except for one issue with Kerberos authentication, which I am in the process of fixing. So maybe you are hitting something like that, or maybe you just need a settings tweak. I'm not sure why you would've needed to disable U2U or the certificate prompts in xfreerdp.

My suggestion is to start with something like this:

  • In the RDP session
    • configure the hostname, username, password in the "General" tab.
    • clear out any VPN you have in the VPN/Tunnel/Gateway section (set "Not enabled")
    • in the "Gateway" tab
      • Set "Use these RD Gateway Server settings"
      • Server name = Gateway host name
      • Logon method = "Ask for Password (NTLM)"
      • And then either
        • Check "Use my RD Gateway credentials for the remote computer". Note the naming here follows Microsoft, but it's actually inverted. It means "use the credentials for the RDP server for the Gateway", i.e. use what you configured in the first step
        • Press "Credentials" and enter the Gateway username, domain (if needed) and password. Make sure it's set to "Store password in the database", that should be the only option.


Screenshot 2026-09-15 at 20.51.36.png
Now try the connection. If it works, great; but my guess is you tried all of this already and it didn't work, but we need to understand why.

So, close RDM; then switch to your terminal and set the environment variable WLOG_LEVEL to "Debug", then relaunch RDM from the same terminal. You might consider redirecting stdout and stderr to a file at the same time. Something like this:

export WLOG_LEVEL=DEBUG
remotedesktopmanager > ~/Desktop/rdm-rdp.txt 2>&1


RDM will launch; try your connection again and you should have a log file on the configured path. Please zip it and send it to me by PM here on the forum.

I hope it's clear, but if you have any questions or problems please don't hesitate to reach out

Kind regards,

Richard Markievicz

Screenshot 2026-09-15 at 20.51.36.png