Quick answer: For a graphical client, install Remmina (sudo apt install remmina on Ubuntu/Debian), create a new RDP connection profile, and enter your server's IP, username, and password. For scripting or servers without a desktop, use FreeRDP: xfreerdp /u:username /p:password /v:server-ip. Both support modern RDP with Network Level Authentication.

The Linux RDP clients compared

Three clients cover essentially every Linux RDP need. Remmina is the default recommendation: a GTK graphical client preinstalled on Ubuntu and many derivatives, with tabbed sessions, saved profiles, and support for RDP, VNC, SSH, and SPICE in one window. If you want to click through a setup and save connections visually, start here.

FreeRDP (the xfreerdp command) is the engine under Remmina's RDP support, exposed directly. It is the choice for automation — connection strings in scripts, one-off connects from a terminal, servers without any graphical environment. It tracks the RDP protocol closely, including NLA, gateways, and clipboard and drive redirection flags. The learning curve is a man page, but the payoff is total scriptability.

rdesktop is the elder of the family: tiny, stable, and long unmaintained. It still works for basic connections to older servers but lacks modern features and should be your last resort, not your first. For completeness: GNOME Connections is a minimal modern frontend some distributions ship, fine for occasional use but thinner on options than Remmina.

ClientInterfaceBest forWatch out for
RemminaGraphical (GTK)Daily desktop use, saved profiles, tabbed sessionsPlugin packages needed for full protocol support on some distros
FreeRDP / xfreerdpCommand lineScripting, servers, quick connects, automationFlags change between versions; check the man page
rdesktopCommand line / minimalLegacy servers, minimal installsUnmaintained; no modern RDP features
GNOME ConnectionsGraphical (minimal)Occasional simple connectsFew tuning options

Under the hood, Remmina's RDP support is FreeRDP, so protocol behavior — NLA handling, redirection, encryption — is consistent between them. Your choice is really about interface: GUI profiles versus terminal commands. Many Linux admins end up with both installed: Remmina for interactive work, xfreerdp in scripts.

FreeRDP protocol engine NLA · redirection · encryption Remmina (GUI) profiles · tabs · clicks xfreerdp (CLI) scripts · flags · automation Same engine, two interfaces — behavior matches, workflow differs.
Fig. 1 — Remmina and xfreerdp share the FreeRDP engine; pick by workflow.

Remmina: install and connect

On Ubuntu and Debian, Remmina is often preinstalled — check your applications menu first. If it is missing, install it with sudo apt install remmina remmina-plugin-rdp; the plugin package matters, because some distributions split protocol support out of the base install. Flatpak users can install the Flathub build instead, which tends to be newer.

Connecting is straightforward: open Remmina, click the + to create a profile, set Protocol to RDP, and fill in Server (your server's IP), Username, and Password — for example, the credentials from your RDP Temple welcome email. (Your client area login is for billing, not for the server itself.) Set a profile Name like "Main VPS," choose your color depth and resolution on the Basic tab, and click Save and Connect.

Worth configuring on the Advanced tab: share your home folder for file exchange (the Linux equivalent of drive redirection), clipboard synchronization (on by default — if it misbehaves, our clipboard fix guide applies here too), and sound redirection if you need remote audio locally. Remmina's tabbed interface really shines once you have several profiles: one window, many servers, each a tab.

FreeRDP: the command-line power tool

Install it with sudo apt install freerdp2-x11 (package names vary slightly by distribution; on newer releases look for freerdp3). The basic connect is one line: xfreerdp /u:youruser /p:yourpass /v:203.0.113.10. Add /f for full screen, /multimon for all monitors, /clipboard to ensure clipboard redirection, and /home-drive to share your home directory with the session.

Where FreeRDP earns its keep is scripting. A deploy script can open a session, and combined with /app: you can launch a single remote application instead of a full desktop — handy for running one Windows-only tool from a Linux workstation. Credentials in scripts deserve care: prefer environment variables or a credentials file with tight permissions over plaintext passwords in shell history. For managing many such connections with a GUI, see our RDP connection manager roundup.

Version note: FreeRDP 2.x and 3.x use slightly different flag syntax in places. If a flag from a tutorial errors out, check man xfreerdp on your installed version before assuming the tutorial is wrong — the man page is authoritative for your build.

Certificates, NLA, and gateways

Three Linux-specific gotchas, all solvable. First, certificates: on first connect, FreeRDP-based clients warn that the server's certificate is unknown. This is expected for a new server — verify the fingerprint against your provider's details if they publish it, then accept. If the warning reappears every connect, the client may not be persisting known hosts due to permissions on ~/.config/freerdp; check that directory is writable.

Second, NLA: modern Windows servers require Network Level Authentication, and both Remmina and FreeRDP support it — but very old client builds may not. If you see an NLA-related error, update the client before changing the server; disabling NLA server-side to accommodate an ancient client is the wrong trade. Our NLA guide explains what the setting does and how to configure it properly.

Third, gateways: if your provider or employer routes RDP through an RD Gateway, Remmina has gateway fields on the profile's Advanced tab, and xfreerdp takes /g:gateway-address /gu:user /gp:pass. Most individual hosted servers need no gateway at all — only fill these in if you were explicitly given gateway details.

✓Install: remmina + rdp plugin, or freerdp2-x11 ✓Profile: server IP, username, password ✓First connect: verify and accept the certificate ✓Enable clipboard sync + home folder sharing
Fig. 2 — The Linux first-connection checklist.

Get connected: the practical path

  1. Pick your client. Interactive daily use: Remmina. Scripting or terminal-only: FreeRDP.
  2. Install it. sudo apt install remmina remmina-plugin-rdp or sudo apt install freerdp2-x11 on Ubuntu/Debian.
  3. Create the connection. Remmina: new RDP profile with server IP, username, password. FreeRDP: xfreerdp /u:user /p:pass /v:ip.
  4. Accept the certificate on first connect after verifying it is your server.
  5. Enable clipboard and folder sharing so copy-paste and file exchange work immediately.
  6. Set resolution and color depth to suit your monitor and connection speed.
  7. Save the profile (Remmina) or alias the command (FreeRDP) so reconnecting is one click.
  8. Test the session basics: copy-paste both ways, audio if needed, and file transfer via the shared folder.

If you also connect from other platforms, the Android, iPhone, and Mac guides cover those clients. And if the session's display looks wrong once you are in, the display resolution guide sorts out sizing and scaling.

Need an RDP server that just works?

Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan.

Shared Servers$6/mo
Dedicated Server$165/mo
Get Started

3-day money-back guarantee · Dedicated IP on every plan · 24/7 support

RDP Clients for Linux: FAQ

Remmina is the best default: a polished graphical client with saved profiles, tabbed sessions, and RDP support via the FreeRDP engine. Use FreeRDP's xfreerdp directly when you want command-line connections or scripting.

Run sudo apt install remmina remmina-plugin-rdp. The plugin package is important on distributions that split protocol support out of the base install — without it, RDP may not appear as a protocol option.

A basic connection looks like xfreerdp /u:username /p:password /v:server-ip. Add /f for full screen, /clipboard for clipboard redirection, and /home-drive to share your home folder with the session.

FreeRDP-based clients warn on first connect because the server's certificate is not yet known. Verify the fingerprint against your provider's details if published, then accept it — the warning should not repeat on later connects.

Yes. Both Remmina and FreeRDP support NLA, which modern Windows servers require. If you hit an NLA error, update the client rather than disabling NLA on the server.

Yes. In Remmina, enable folder sharing on the profile's Advanced tab; with xfreerdp, use the /home-drive flag. The shared folder appears inside the Windows session as a redirected drive.