RDP legacy mode
Hi Team,
We found several external RDP hosts where the standard RDP engine does not work and we had to switch to the legacy mode to get it working. I attached the log files of one connection with and one without the legacy mode enabled. The RDM version is 2021.1.3.0 on MacOS and the server is running Windows Server 2012 R2.
As these errors are mentioned in the log files:
- Yes, we also tried to disable NLA, but that didn't help
- Yes, the user credentials are correct and does work if legacy mode is enabled
Is there anything else we can try or need that to be fixed in RDM?
BR Andreas
non-legacy-mode.log
legacy-mode.log
All Comments (8)
Hi Andreas,
We use FreeRDP (in both Legacy and Modern) as our engine for RDP sessions. The main differences between the two would be that Legacy uses a version of FreeRDP that has not been updated since 2016 while Modern uses a more recent version of FreeRDP (from about a year ago). My first question would be, are you able to make the sessions in question works with FreeRDP latest (using xfreerdp)?
Best regards,
Xavier Fortin
Hi Xavier,
Yes, it works with the latest version (installed yesterday via brew install freerdp --HEAD).
Best regards
Andreas
Hi Andreas,
Can you share the command you used to connect with xfreerdp? You can replace any sensitive information, I just want to make sure that everything your using is properly implemented in the Modern engine.
Best regards,
Xavier Fortin
Hi Xavier,
the command was: xfreerdp -u username 10.x.x.x
The domain and password were typed in during the connection process.
Best regards
Andreas
Hi,
Thanks for this. We will investigate this. It might requires an update of our FreeRDP component (which can take a while). For the moment, keep using the Legacy engine if it works on those sessions.
Best regards,
Xavier Fortin
Hi Xavier,
Thank you, I'm looking forward to the update in the future.
Best regards
Andreas
I have the same issue. when I use the new RDP engine.
But after I did some tests for different remote servers (some of them are standalone servers, some of them are member servers within domain).
I found only servers within domain and load credentials from vault has this issues.
And after checked FreeRDP GitHub issue list, I found this caused by new FreeRDP engine not support /u:DOMAIN\USER anymore, the new version only support /d:DOMAIN /u:USER.
If you save your credentials in vault and use DOMAIN\USER format, it will cause the error.
After I update the credential format, I can connect with new engine without any issue.
Hi htchen829remote,
Thanks for taking the time to post this information!
Best regards,
Xavier Fortin