Setting Up Remmina Remote Desktop on elementary OS
Remmina has long been a favourite tool among Linux users who need to reach a Windows machine, a macOS host, or another Linux box from their workstation. On elementary OS, it slots neatly into the Pantheon desktop without dragging in heavy dependencies or a cluttered interface. The application supports a wide range of protocols, which makes it suitable for sysadmins in Perth studios, developers bouncing between Sydney and Brisbane, or anyone running a homelab in Adelaide.
For many Australians, working remotely has become a daily reality. According to the Australian Bureau of Statistics, hybrid and fully remote arrangements remain common across knowledge work, and the federal government's flexible work guidelines encourage employers to support distance collaboration. Pairing that reality with the variability of the National Broadband Network means your remote desktop client needs to be both resilient and easy to tune.
Remmina ships with protocol plugins for RDP, VNC, SSH, SPICE, and XDMCP, so you can manage a single server farm from your laptop or pop into a Windows machine that hosts a piece of legacy software. It also handles credential storage through GNOME Keyring, which is helpful when working under Australia's Privacy Act 1988 and the Australian Privacy Principles, where reasonable steps to protect authentication material are part of baseline compliance.
Because the tool is open source, lightweight, and consistent with the elementary OS ethos of thoughtful design, it deserves a proper setup guide. The following walk-through covers installation, connection creation, profile management, and a few practical tweaks for the realities of Australian internet infrastructure.
Why Remmina Fits Well into the elementary OS Workflow
The Pantheon desktop that powers elementary OS is built around clarity and restraint. Remmina shares that sensibility: its main window lists saved connections, and each one can be expanded to show configuration details. Nothing about the application fights against the rest of the system, and its reliance on GTK means it respects your theme choices, whether you use the default elementary look or a custom variant.
Remmina is also a long-term project maintained by the FreeDesktop community. It receives steady updates, which matters when you depend on it for daily work. The application's plugin architecture lets you load only the protocols you need. RDP and SSH are typical essentials, but you can disable components you do not use to slim down the install.
For Australian users juggling connections between capital cities, Remmina supports multiple profiles with separate settings. You can keep a high-quality profile for connecting across the NBN to a machine in your home office in Melbourne, and a lower-bandwidth profile for when you are travelling in regional Queensland where latency and throughput are less predictable. That flexibility makes it easier to maintain productivity regardless of where you are working from.
Installing Remmina Through the AppCenter
The most straightforward path to a working install is through the elementary OS AppCenter. Open the AppCenter from the dock or the Applications menu and search for "Remmina". The official package is published there, so you can install it with a single click without leaving the curated store.
Once installed, launch Remmina from the Applications menu. The first time you open it, the application will ask whether it may access the GNOME Keyring to store passwords. Approve the prompt if you intend to save credentials. The keyring integration ties in with the system's Secret Service API, which is the same backend used by other Pantheon components.
After the initial launch, take a moment to explore the Preferences menu. You can choose the default protocol, set the resolution for new connections, and decide whether Remmina should minimise to the system tray when you close the main window. Adjusting these defaults early saves time when you create dozens of profiles later on, especially if you manage hosts for clients in different time zones across Australia.
Alternative Installation Methods with Flatpak and apt
If you prefer Flatpak, or if you want a more recent build than the one in the AppCenter, Remmina is available on Flathub. From a terminal, run:
flatpak install flathub org.remmina.Remmina
Flatpak builds tend to track upstream releases closely and arrive in a sandboxed environment. This can be helpful if you are working in a corporate setting where system packages are pinned, or if you simply want isolation between Remmina and the rest of your desktop.
For users who prefer the traditional Debian package path, Remmina also appears in elementary's repositories. You can install it with apt:
sudo apt update sudo apt install remmina remmina-plugin-rdp remmina-plugin-vnc remmina-plugin-secret
The plugin packages are worth installing individually because the base application does not pull in every protocol handler by default. The RDP plugin, in particular, is essential for connecting to Windows machines, and the secret plugin enables password storage through the keyring.
Whichever method you choose, log out and back in afterwards so the Remmina desktop entry registers correctly with the system. Some sessions cache application launchers, and a fresh login avoids the confusion of clicking an icon that does nothing.
Building Your First Remote Desktop Connection
Creating a profile in Remmina is straightforward. Click the plus icon in the top-left corner or use the Connection menu. A dialog appears with fields for protocol, server, username, password, and resolution. Choose the protocol that matches your target machine: RDP for most Windows hosts, VNC for cross-platform screen sharing, SSH for command-line-only access, and SPICE for virtual machines running under QEMU or KVM.
Give the profile a descriptive name. Naming conventions matter when you have several connections to manage. A common approach is to include the location and role, such as "Sydney Office - Fileserver" or "Brisbane Studio - Backup PC". This makes the connection list easy to scan and reduces the risk of launching a session against the wrong host.
Set the colour depth and quality to suit your network conditions. The NBN delivers asymmetric speeds to most Australian households, which means upload bandwidth is often the bottleneck. If you are connecting from home to a machine at work, choose a medium quality setting. If you are inside a corporate LAN, you can push the quality higher because there is plenty of bandwidth available.
Save the profile and double-click it to test the connection. Remmina opens the remote session in a tabbed window, allowing you to switch between multiple hosts without juggling separate windows. The tabbed interface is a small feature that pays off quickly when you are working across several machines at once.
Tuning Display, Colour Depth, and Resolution
Once a session is open, you can fine-tune the experience without editing the profile. Use the View tab in the connection window to toggle fullscreen, fit the remote desktop to your window, or scale the display. These options are particularly useful when working on a small laptop screen while travelling, where every pixel matters.
Colour depth affects both visual fidelity and bandwidth. A 32-bit colour session looks crisp but consumes more data. On a stable NBN FTTP connection in suburban Adelaide, you can usually sustain high quality without noticing lag. On a wireless link in a regional town, dropping to 16-bit colour reduces traffic and helps the session stay responsive.
Keyboard handling is another area worth configuring. Remmina can capture and release the keyboard with a hotkey combination, which defaults to Ctrl+Alt+Enter. If you use a custom shortcut elsewhere on your system, remap it in the preferences to avoid conflicts. The same goes for clipboard sharing; if you frequently copy text between local and remote machines, make sure clipboard synchronisation is enabled.
Audio forwarding depends on the protocol. RDP supports audio redirection natively, while VNC requires additional setup. If you need to hear audio from the remote machine, such as a media workstation running in Perth that you only reach remotely, configure the audio plugin in Remmina's preferences. Some users prefer to route audio over a separate channel, particularly when latency is high.
Managing Profiles and Securing Credentials
Remmina stores profiles in an SQLite database inside your home directory, typically under ~/.local/share/remmina. Each profile is a small file containing connection parameters, including the password if you opted to save it. For Australian users subject to the Notifiable Data Breaches scheme under the Privacy Act, treating that database as sensitive material is wise.
Take advantage of GNOME Keyring for credential storage rather than embedding plaintext passwords in profiles. The keyring encrypts secrets with a master password tied to your login session. When you choose to store a password in Remmina, it is routed through the keyring rather than written in clear text. Avoid creating profiles that store passwords if you share your machine with others.
If you need to back up or migrate profiles, Remmina provides an export feature. You can save a profile as a single file, then import it on another machine. This is helpful for users who maintain both a desktop and a laptop, or who work across two machines in different cities. The exported file still contains the password if the keyring was used, so keep the export file in a secure location.
Periodically review your list of saved profiles. Over time, hosts get decommissioned, IP addresses change, and projects end. Removing obsolete profiles keeps the list tidy and reduces the risk of accidentally connecting to a machine that has been repurposed. It also makes it easier to audit which systems you have access to, which is a useful habit under any compliance regime.
Troubleshooting Common Connection Issues
Connection failures happen, and Australian networks have their own quirks. If a session refuses to start, the first thing to check is the protocol selection. RDP defaults to port 3389, while VNC uses 5900 plus the display number. Firewalls on either end of the connection may block these ports, especially on consumer routers supplied by Telstra, Optus, or TPG.
Latency spikes are common on NBN services, particularly during peak evening hours. If you notice the remote desktop becoming sluggish, drop the colour depth or disable wallpaper rendering in the RDP profile. Both changes reduce the amount of data sent per frame, which helps when the connection struggles.
Authentication errors often point to credential mismatches. Verify the username format expected by the remote host. Windows machines typically want "DOMAIN\username" or just "username", while Linux servers often expect a plain Unix account. Remmina lets you set the domain field separately, so check that it matches what the server expects.
If the session opens but the keyboard layout is wrong, change the keyboard map in the profile or session settings. Australian users typically use the US or US International layout, but some servers expect UK layouts, especially legacy systems. Pick the layout that matches the server's expectation rather than your local layout to avoid strange typing behaviour.
Remmina rewards a small amount of upfront configuration. Set sensible defaults, choose your protocol plugins deliberately, and store credentials through the keyring. Once that foundation is in place, the application becomes a quiet tool that does its job without demanding attention, whether you are working from a home office in Hobart, a co-working space in Canberra, or a regional hub where the NBN connection is the limiting factor. Keep your profile list lean, revisit it occasionally, and let Remmina handle the legwork for your remote sessions.
