Skip Navigation
18 comments
  • This is the best summary I could come up with:


    FreeRDP 3.0 continues getting better for this open-source solution for interoperability with Microsoft RDP for remote desktop purposes.

    Released at the end of July was the FreeRDP 3.0 beta for this open-source Remote Desktop Protocol (RDP) implementation.

    FreeRDP 3.0 is bringing AAD/AVD authentication, WebSocket Transport, SmartCard emulation support, OpenSSL 3 support, a new reference client based on SDL2, and a wide array of other improvements for this remote desktop/GUI handling solution for interoperability with Microsoft's RDP on Windows.

    With today's FreeRDP 3.0 Beta 2 release there is improved AAD support, improved HTTP gateway failure logging, improved shadow server error handling, CMake build system enhancements, the SDL client now has basic multi-monitor support, improved MinGW build support, and various other enhancements.

    Downloads and more details on the FreeRDP 3.0 Beta 2 release via GitHub.


    I'm a bot and I'm open source!

  • I've been using it through remmina for years at this point and I've rarely had a problem with it. Big thank you to the developers

    • Same. Except I use krdc. There's a weird bug where sometimes it stops accepting input at random. Hoping this release has a fix.

  • So can I install this on a Windows Home PC (which doesn't allow incoming rdp connection by default) and access it through Linux? I know there is rdpwrap, but it hasnt been updated last I checked

    I couldn't find any clear info on this.

    • Freerdp is a client not the server. As far as I know for windows you’d need to use something like no machine or teamviewer for that kind of functionality (or upgrade to pro for the rdp function)

      • @socphoenix @On RDP server and client is Microsoft built-in, but bound to license restrictions. In general, 2 concurrent rdp sessions on one machine are possible without a need to extend the standard Windows license / price. You can add and license the rdp services role / terminalserver role to a machine setup and have more flexibility: more users, more administration of user sessions.

        If your target is a Windows machine, you need a user that is a member of the target machine's local rdp or local admin security group, either directly or via a domain security group, start a client software (below) depending on your machine's operating system, enter the target machine's address (ip or name) and user name and password, and have a desktop session on the target machine in a window to remote comtrol it. You might need a VPN or citrix connection to the target's domain and you might need to qualify a user domain of your login credentials, but that's it in general.

        1/x

    • To access Linux from Windows, you need to install xrdp in Linux, if using Ubuntu there was some install problem and a guy made a script to properly install it.

      To access windows from Linux, use remmina in Linux, it works pretty well I'm using it daily. Remmina can use a lot of remote protocol, FreeRDP is one of them.

18 comments