Hi!
can you try the wfreerdp.exe which ships with Royal TS? Once you open a connection you should see the executable in %temp%. Use that one to test against your server.
If that one also works as expected it may be related to the way we embed wfreerdp.exe. We are utilizing the /parent-window argument to redirect drawing and input handling to a different window handle (inside of Royal TS).
Regards,
Stefan
Hi Stefan,
I tried the wfreerdp.exe which ships with RoyalTS and I was able to establish a working connection.
Regards,
Daniel
I've just created a new Royal TS V7 Beta Build which also includes the latest wfreerdp.exe:
x64 MSI: https://download.royalapps.com/RoyalTS/RoyalTSInstaller_7.00.20219.0_x64.msi
x64 ZIP: https://download.royalapps.com/RoyalTS/RoyalTS_7.00.20219.0_x64.zip
ARM64 MSI: https://download.royalapps.com/RoyalTS/RoyalTSInstaller_7.00.20219.0_ARM64.msi
ARM64 ZIP: https://download.royalapps.com/RoyalTS/RoyalTS_7.00.20219.0_ARM64.zip
Please note that this build hasn't been fully tested yet but I wanted to let you try this build as soon as possible to see if the new wfreerdp.exe fixes the issue.
Looking forward to your feedback. Thanks!
Hi Stefan,
i just tested your version of RoyalTS and everythink works as it shoul.
Thank you for your great support!
regards
Daniel
That's great to hear. Thanks for letting us know.
cheers,
Stefan
Daniel Breisacher
Hello,
we are currently using the Beta Version of RoyalTS and establish connections to Windows Servers over wfreerdp which is using a SOCKS5 proxy. Everything works fine with this setup except the connections to Windows 2008 Servers. After the connection you can see the screen but you are totaly unable to do anything, the remote machine is totally freezed. For test purposes I downloaded freeRDP and tried to connect to the servers by my own and everthing worked. So I guess it has nothing to do with our servers or freeRDP.
Do you have any ideas what could be the reason for this behaviour?
regards
Daniel