changing transport type (from default to RPC) in Microsoft RDP Gateway entity is not taking effect
changing transport type (from default to RPC) in Microsoft RDP Gateway entity is not taking effect
RDM version: 2022.3.19.0 (MAC)
although I've changed the transport type to RPC in an Microsoft RDP Gateway entry, RDM still use transport type HTTP to connect to the RDP Gateway.
The only way to make it work for now, is, go to the RDP entry (the host you want to connect via RDP Gateway), go to the Gateway tab and fill in the RDP Gateway info, instead of using the VPN/SSH/Gateway under connection section on the left panel.
the reason that I want to use transport RPC instead of HTTP is due to a freerdp issue. RDM use freerdp for RDP connection if I am not mistaken. In our environment, we enabled SSL offload (https <-> http) on Windows 2022 RDP Gateway servers. After that, RDM always got error "ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED". The case is very similar to https://github.com/FreeRDP/FreeRDP/issues/5937.
All Comments (7)
Hello,
Thank you for reaching out to us regarding this,
I will open a ticket to our QA department to see if they are able to reproduce this behavior,
I will keep you updated with any news I receive.
Best regards,
Samuel Dery
Hi Samuel,
The previous test was on MAC. I just did another test on RDM windows version 2022.3.35.0 64bit. It doesnt have the transport option in Microsoft RDP entry and Microsoft RD Gateway entry, but it also doesnt experience the "ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED" error so RDM windows version is good. The issue is for RDM MAC version only.
Best regards,
Eric
Hello,
Thank you for your reply and for the additional information,
I will add this to the ticket.
Best regards,
Samuel Dery
Hi pirate585,
There indeed seems to be an issue in carrying the Transport setting from the RDGateway entry to the RDP entry. I've made the change and we will inform you when a version is available with it.
Best regards,
Xavier Fortin
cool...that's a quick response/fix
Hi pirate585,
RDM Mac 2023.1.7.0 is now available with a fix for this.
Best regards,
Xavier Fortin
thanks a lot
