I wanted to be able to help someone with their Ubuntu laptop when they call with a problem. That means seeing the same screen they see, moving the mouse when needed, and connecting without making them hunt through menus to approve every session. The Internet connection can be awful, so I wanted something compressed too. In my head this was a ten minute job: install a VNC server, add an SSH tunnel, open a viewer. Ubuntu had other ideas.
The first surprise was that I was asking for the screen and GNOME kept offering me a session. The second was that its two remote desktop switches use the same protocol but do completely different things. I got a black laptop display, a GDM login screen, a warning about closing my applications, and finally a white Remmina window while trying to work out which one I had connected to. WTF.
Here is the setup that actually worked for me. The Ubuntu laptop I configured runs Ubuntu 26.04.1, GNOME Shell 50.1 and Wayland. I kept the built-in GNOME remote desktop server and used RDP over Remmina’s built-in SSH tunnel. I also used NetBird to reach it through firewalls; that part is optional if you already have a route to its SSH server. No new desktop environment or pile of VNC packages.
Check which Ubuntu/GNOME you have
On the machine whose screen you want to see, open a terminal inside its desktop and run:
grep PRETTY_NAME /etc/os-release
gnome-shell --version
echo "$XDG_SESSION_TYPE"
grdctl --help
Mine said Ubuntu 26.04.1 LTS, GNOME Shell 50.1 and wayland. Its grdctl --help listed rdp commands and no vnc commands. Check that last one on your installation: upstream GNOME documents VNC, but the Ubuntu package I actually had did not expose it. wayvnc does not support GNOME’s compositor. An old X11 screen scraper cannot see this Wayland desktop either. Xvnc would give me an independent virtual X desktop, which is a different problem from controlling the physical screen.
GNOME’s RDP server was already there. RDP also has a reasonable chance on a rotten connection: it encodes and compresses the desktop, and Remmina has settings to cut visual effects. So I stopped fighting for the vncviewer -via ... command I had originally imagined.
Get an SSH route to the laptop
NetBird is optional. If your administrator laptop can already reach the Ubuntu machine over a LAN, an existing VPN, or another trusted route, skip this installation and use that reachable hostname or address in the SSH and Remmina steps below. I chose NetBird because I wanted to retain access when both laptops are behind firewalls, without asking anyone to configure a router.
If you want the same route, install NetBird on both machines and join them to the same NetBird network. The official Linux instructions use:
curl -fsSL https://pkgs.netbird.io/install.sh | sh
sudo systemctl enable --now netbird
netbird up
netbird status
The first netbird up needs a one-time sign-in. A machine without a usable browser can use a NetBird setup key instead; protect that key like a password. Use the NetBird name or address when you connect over SSH. NetBird can use relays when a direct connection is impossible, so it helps with awkward networks without promising that every firewall will permit a direct path.
Why NetBird instead of Tailscale? This is where I get grumpy. Tailscale does use the WireGuard protocol, but its own comparison with WireGuard says its Linux client uses a userspace WireGuard implementation with more overhead than the kernel module. NetBird uses the Linux kernel WireGuard path by default when the module is available. On my Ubuntu laptop, netbird status -d reported Interface type: Kernel. That is the path I wanted. A blank sudo wg listing for Tailscale only tells you that it has no kernel WireGuard interface; it does not mean its tunnel is fake or unencrypted. But why add userspace tunneling overhead on Linux when the kernel implementation is right there? For remote support over a miserable connection, that design choice is stupid. I have not benchmarked the two products on this laptop, so I am not inventing a speed number.
On the Ubuntu machine, install and start OpenSSH Server:
sudo apt update
sudo apt install openssh-server
sudo systemctl enable --now ssh
On the administrator’s laptop, create a key only if you do not already have a trusted one, then install its public half for the Ubuntu account. Substitute the account and whichever reachable hostname you use for alice and ubuntu-laptop:
ssh-keygen -t ed25519
ssh-copy-id -i ~/.ssh/id_ed25519.pub alice@ubuntu-laptop
ssh -o BatchMode=yes alice@ubuntu-laptop true
Do not overwrite an existing private key when ssh-keygen asks. The last command should succeed without asking for the account password; check the SSH host fingerprint the first time. The private key stays on the administrator’s laptop. Remmina will use the same SSH key via the SSH agent.
Share the actual screen on port 3390
Log in to the Ubuntu desktop locally. Open Settings → System → Remote Desktop → Desktop Sharing, enable Desktop Sharing and Remote Control, and set an RDP username and password. These are separate from the Ubuntu account password. Pick a strong password, put it in a password manager, and keep it out of shell history and screenshots.
I chose a fixed port to keep the two GNOME modes apart. Run these commands as the logged-in desktop user:
grdctl rdp set-port 3390
grdctl rdp disable-port-negotiation
grdctl rdp disable-view-only
grdctl rdp enable
systemctl --user enable --now gnome-remote-desktop.service
grdctl status
If you prefer to enter the RDP credentials in a terminal, grdctl rdp set-credentials prompts for them. The credentials are static until you change or clear them; restarting GDM or rebooting does not invent a new password. Do not run grdctl status --show-credentials in a screenshot or a public terminal recording.
There is a nasty limitation here: Desktop Sharing shares an existing logged-in desktop. Ubuntu’s own documentation says you must be logged in before someone can connect. Locking the screen can end the remote-assistance connection. If the machine reboots and sits at GDM, port 3390 cannot magically show the old session. Automatic login may create a session, but it gives anyone physically at the laptop access to the account, and a locked GNOME keyring can still prevent the stored RDP credentials from working. I have not verified an unattended reboot into a shareable physical screen, so I would not sell this as one. My tested setup works when the local desktop is logged in.
For a machine that must remain reachable while idle, check Settings → Power → Automatic Suspend and the laptop lid behavior. Display blanking and suspension are different things: if the laptop suspends, the network route, SSH and RDP are all gone until it wakes. Keeping a local session unlocked also has an obvious physical-access cost.
The confusing other port: 3389
Settings → System → Remote Desktop → Remote Login is a different GNOME service. Mine listens on 3389 and is available before a local user logs in. It first asks for the Remote Login RDP credentials, then shows a GDM login where you enter the Ubuntu account password. It creates a separate graphical session. The laptop’s own display can stay at GDM while you work remotely. That is why it looked as if the laptop screen had switched off.
If the same Ubuntu account is already in a local session, GDM may ask to terminate it. Read that warning! Continuing can close applications in the session you meant to control. I keep Remote Login as a fallback for reaching a machine at the login screen, not as my screen-sharing profile.
To see what is enabled on your machine:
grdctl status
sudo grdctl --system status
sudo ss -ltn | grep -E ':(3389|3390) '
The first status is the logged-in user’s Desktop Sharing service; --system is Remote Login. In my setup 3390 = physical screen, 3389 = separate remote login. Both speak RDP, despite my original VNC plan.
Make Remmina open the SSH tunnel for you
On the administrator’s laptop, open Remmina and click + to create a profile. Choose RDP and give it a name such as Ubuntu laptop (screen). In the Basic tab:
- Server:
localhost:3390 - Username: the Desktop Sharing RDP username, not necessarily the Ubuntu account name
- Password: the static Desktop Sharing RDP password
- Color depth: start with Automatic
In the SSH Tunnel tab:
- Enable SSH tunnel.
- Enable Tunnel via loopback address.
- Choose Manual for the SSH server and enter the Ubuntu laptop’s reachable hostname or address (its NetBird name, if you chose NetBird; for example
ubuntu-laptop). - Enter the Ubuntu SSH account name separately (for example
alice). - Use SSH agent if your key is loaded, or select your private key file in Remmina.
In Advanced, enable Ignore certificate for this specific profile if Remmina rejects GNOME’s local RDP certificate: the RDP connection is inside the SSH tunnel, whose host key you already verified. Save the profile and double-click it. Remmina opens the SSH tunnel itself and then connects to port 3390 on the Ubuntu laptop. No separate ssh -N -L ... terminal is needed.
The localhost:3390 value looks weird until you know what Remmina is doing: with Tunnel via loopback address, it means port 3390 on the remote laptop. I initially had localhost:23390, which only makes sense if I have already started a manual ssh -L tunnel on the administrator’s laptop. With Remmina managing the tunnel, that old value produced “failed to connect to localhost”.
For a bad link, lower the Ubuntu machine’s display resolution, avoid animated wallpaper and try Remmina’s low-bandwidth or poorer-quality setting. Text at a modest resolution is more useful to me than a beautifully compressed high-resolution desktop that updates once a week. RDP already compresses its graphics; piling SSH compression on top is unlikely to help.
I made a second Remmina profile for Remote Login on 3389, but left its SSH tunnel off and used the laptop’s NetBird name directly. With Remmina’s tunnel on, GNOME’s RDP login handover left me with a white window; direct RDP over encrypted NetBird completed it. If you skipped NetBird, use this direct profile only across a network path you trust and can reach. That profile opens a separate GDM session. The first profile is the one that shows the laptop’s screen.
So yes, I can now click one Remmina profile and see the same desktop as the person at the Ubuntu laptop, over SSH and, in my case, NetBird. They do not need to approve a prompt each time. They do still need to be logged in to that desktop. GNOME made a simple VNC-shaped IT support wish surprisingly complicated, but at least the working path uses what Ubuntu already ships.
Further reading: Ubuntu’s remote desktop guide, GNOME Remote Desktop configuration, Ubuntu OpenSSH setup, NetBird Linux installation, and wayvnc’s supported compositors.
