Users

All Posts (1)

avatar

htchen829remote

RDP legacy mode

avatar
avatar
avatar
avatar

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.

1 - 1 of 1 items