KDE Plasma has a built-in RDP server for Wayland sessions. I use it when I need access to an Arch or Gentoo workstation in my homelab without adding another VNC server and its configuration.
The setup is quite simple, but it is important to understand that Plasma Remote Desktop shares an existing graphical session. It is not a replacement for a full remote login server on a machine which is powered off, suspended or stuck at the SDDM login screen.
Requirements for KDE Plasma Remote Desktop
KDE's RDP implementation is provided by krdp. It uses the Wayland and PipeWire infrastructure already available in Plasma, so it does not need an Xorg display or a separate VNC stack.
First I check that I am actually running a Wayland session:
$ echo $XDG_SESSION_TYPE
wayland
If this prints x11, log out and select a Plasma Wayland session in SDDM. The Remote Desktop page may still be visible on X11, but the current Plasma RDP implementation is meant for Wayland.
On Arch Linux I install the package like this:
# pacman -S krdp
On Gentoo the package is part of the KDE Plasma packages:
# emerge --ask kde-plasma/krdp
After installing it, log out and back in once if the Remote Desktop page was not available before. Plasma starts and manages the RDP server from your user session. There is no separate system-wide daemon which I would manually enable with systemctl.
Do not install
x11vncor another VNC daemon next to this unless you really need it. Two remote desktop services listening on the same workstation are just extra things to maintain.
Enabling the RDP server in Plasma
Open System Settings, then go to System and select Remote Desktop.
There I enable the RDP server and configure these settings:
- Enable remote desktop sharing
- Allow remote control, not only view access
- Set a dedicated RDP user name
- Set a long, separate password
Plasma normally shows the connection details in this page as well. I still prefer to use the workstation IP address from my DHCP server or a local DNS name, rather than relying on a changing address.
To see which address the machine currently has, I use:
$ hostname -I
192.168.1.42
The RDP service listens on TCP port 3389. You can verify that after enabling it:
$ ss -ltn | grep 3389
LISTEN 0 128 *:3389 *:*
Seeing *:3389 is normal. It also means the firewall is important, because the RDP server may otherwise be reachable from networks where you do not want it.
Restricting RDP with firewalld
I would not expose Plasma RDP directly to the Internet. A password prompt on port 3389 is not a public-facing remote access solution, imho.
On systems where I use firewalld, I first check the active zone:
# firewall-cmd --get-active-zones
home
interfaces: enp4s0
Then I allow RDP only from my local network. Replace the zone and subnet with values matching your setup:
# firewall-cmd --permanent --zone=home \
--add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="3389" protocol="tcp" accept'
# firewall-cmd --reload
success
Check the resulting configuration:
# firewall-cmd --zone=home --list-rich-rules
rule family="ipv4" source address="192.168.1.0/24" port port="3389" protocol="tcp" accept
This is better than simply opening 3389/tcp for every source address. If you have IPv6 enabled in your LAN, add a matching IPv6 rule as well or make sure your firewall policy handles it.
If firewall zones and nftables rules are still a bit confusing, the German Linux firewall training from cmt.de covers the practical differences between firewalld, nftables and older iptables setups.
For access while I am away from home, I prefer a VPN overlay instead of port forwarding. I use Tailscale for this in my homelab, with routing rules kept separate from the RDP service itself. I wrote about the slightly annoying routing part in Tailscale Exit Node on Linux: Policy-Based Routing.
Connecting from a Windows RDP client
Windows already includes an RDP client. Press Win + R, run mstsc, then enter the IP address or DNS name of the Plasma workstation.
Use the RDP username and password configured in Plasma Remote Desktop, not automatically your Linux account password. When Windows asks about the certificate, the warning is expected on the first connection because Plasma creates a local certificate.
For a home network this is usually fine after checking the displayed host name and certificate fingerprint. For a setup used regularly, I keep access inside the LAN or Tailscale network and do not teach Windows clients to blindly accept changed certificates.
The Windows client may initially use an unfitting display size or scaling. I normally set the resolution in the Display tab of Remote Desktop Connection before connecting. Plasma itself handles this reasonably well on a Wayland session, including multiple monitors, but it is still a shared desktop rather than a dedicated virtual Windows-like session.
The unattended access limitation
This is the part which caught me at first. Plasma Remote Desktop shares the currently logged-in Plasma session. It cannot log a user in through SDDM, start a new Plasma session after reboot, wake a suspended workstation or replace an out-of-band console.
That means somebody must log in locally after:
- a reboot or power loss
- a normal shutdown
- a session logout
- a system which suspended while idle
After the user session is running, RDP can be used without somebody sitting in front of the machine. But I would still test the exact locking behaviour on my Plasma version before depending on it remotely. Desktop lock policies, screen power settings and company security policies can change what is possible.
For machines that need to be reachable after every reboot, I use a different layer for recovery, such as IPMI on server hardware, a Proxmox console, or SSH for non-graphical tasks. My workstation disk encryption setup also matters here. With TPM-backed unlocking, as described in LUKS TPM2 Unlock with systemd-cryptenroll and Secure Boot, a reboot can at least bring the machine up without typing a disk password locally, but Plasma still needs a graphical login.
For normal workstation administration though, KDE Plasma Remote Desktop is a nice and clean option. It is already part of the desktop, works with the Windows RDP client and avoids maintaining another VNC service.