7 of the best Linux remote desktop clients

We assess the options for remote viewing


Team Viewer

Download Team Viewer

TeamViewer is quite a big name in the world of Windows and the software has many major corporate clients, but it's little used or considered on Linux. Linux support has been in beta for some time, and the software only runs with the help of Wine. It does work though, and offers features beyond the usual Linux clients.

The first advantage, and in some ways disadvantage, is that this client uses a proprietary protocol that enables clients to link up through a central server, which manages a connection from one site to another.


An advantage is that, with a variety of clients on offer, you can view a remote system from practically anywhere, even on locked-down systems that wouldn't allow an SSH connection, or from behind corporate firewalls. Also, it runs on Windows and Mac, so it's an easy way to cater for all desktops.

The quality of the connection is poor though. It can render a nice desktop at a slow frame rate, or an unreadable desktop at something approaching a nice speed.

However, there are added benefits from the proprietary protocol. It can manage audio (badly) and there's a little chat client, file transfer and some form of VoIP service. We were unable to get the latter working.

Connections are managed by dishing out a PIN on one machine, and the user at the other end typing it in, which isn't as secure as its authors may want you to believe. There's a free version for noncommercial use, although you get an annoying, repetitive popup.

While it has some feature ideas that would be worth implementing in the next generation of Linux remote desktops, at the moment this is a non-starter for Linux.


Web: www.teamviewer.com

Sadly unusable proprietary horrorfest, but it has some nice features, nonetheless.

Rating: 3/10



Download Tiger VNC

As soon as you run TigerVNC, you get a good idea of the kind of people who invented it and why. A tiny request pops up and asks for the server you want to connect to – there are no bookmarks, or lists of located servers on the network. If this were a wrench, it wouldn't be one with a moulded ergonomic grip.

If you click the Options tab though, you'll find there are plenty of settings – ones relating to the connection and the protocols at least. While the software will automatically select the options for you, you can specify things such as colour depth and compression level if you like.


High compression will reduce the bandwidth needed for an effective desktop, at the expense of more CPU cycles being required at both ends. In use, running against the Vino and standard VNC servers, TigerVNC performed reasonably well.

Of the VNC clients, it was much faster than Vinagre, but not quite as responsive as Remmina. There seemed to be a few more refresh problems than most of the other software, with elements of windows shearing off occasionally, and the damaged background not being redrawn for a few seconds.

In terms of response though, it was easy to find the cursor (it renders as a dot, even if the display cursor doesn't keep up) and the keyboard seemed fine. The display is in a single window with scroll bars if it doesn't fit the local screen – there's no scaling, other than running full-screen.

This client is capable enough, and has obviously been designed mainly for admins, but even so, some rudimentary comforts would have been appreciated. You might be a hardened network engineer, but still appreciate not having to type in IP addresses every time you want to connect to something, after all.


Web: www.tigervnc.org

Plenty of options and it runs pretty fast, but there's little UI to speak of. Shortcuts would also be welcome.

Rating: 4/10



Download Vinagre

Although the name of this app sounds like some thing you'd put on a salad, you'll normally find it entitled Remote Desktop Viewer in your Gnome menus, because it's a standard part of the Gnome desktop. On running, an ordinary-looking window opens.

The panel on the right displays discovered servers and any bookmarks. The main part of the window is for the client connection to the server, which can be run full-screen or within the scrollable confines of this window.


If you open multiple sessions with different servers, the remote displays will appear in a series of tabs. The Bookmarks are OK, but can be confusing – there's little to distinguish them from discovered servers.

Like the other VNC clients on test here, it's reliant on the server and the features it supports in terms of performance issues.

We tried Vinagre with the standard VNC server and with its 'other half', Vino. The latter, like Krfb, is a GUI front-end and a VNC server, designed to make it easy to share desktops across computers. We had no trouble connecting to the remote screen, or using the options with the Vino server for features such as JPEG compression or different colour depths.

One curious problem we had was that the cursor often didn't update on the display very frequently. This doesn't seem to be an issue with the connection at all, because menus opened and other GUI elements were displayed almost instantaneously.

Fullscreen mode also proved impossible for us to escape from – the auto-hiding toolbar refused to come out to play, leaving us to yank the rug from under the client to get back to the desktop.


Web: http://projects.gnome.org/vinagre

Simple to use and performs well, if you avoid full-screen mode.

Rating: 5/10


NoMachine NX Client

Download NoMachine NX Client

The NoMachine philosophy is quite simple and easy to buy into. Imagine a world where a computer system has such foresight that even its very method of displaying something on the screen is split into a server-client software relationship. Now imagine that after many, many generations of this, the one true way has been lost, and it's just now a very complicated, overblown display driver.

NoMachine wants X to rediscover its greatness, but too much stuff has been added without thought to the server– client relationship. That's why its approach is completely different to the standard VNC setup.


The NX protocol works over SSH. This brings security and a few other things not native to the RFB protocol used by VNC as standard. It also uses smart methods of encoding and compressing data, and clever use of caches to minimise the bandwidth required. And if you can save the bandwidth, you can do other cunning things with it – why not also ship over the audio feed from the host machine, for example?

An advantage of using the SSH connection is that if you have a user account on the target machine, you can just log in as normal and start a new X session. The corollary is that it's hard to 'grab' a screen that's already running, although the NX machine can do that through a standard VNC connection instead if necessary, or by launching a shadow session.

Shadow sessions work well, and depending on the setup, the remote machine may have to confirm the connection. For whatever reason, this tends to be markedly slower than spawning your own X session.

As well as VNC, it also supports RPC for Windows machines, with a similar interface, so it can be used as a general remote access tool. Although the client software makes it easy to configure connections and save them as settings, it doesn't really give that much love to the desktop users.


Somehow you end up with a whole host (intended) of software installed to do a simple job. There are no tabbed views or anything pretty, and you have to set up sessions in a different application than where you launch them from. But all that goes by the by when you see it run.

Whatever magic pixies sit in the pipes pushing the data through, they do an incredible job. NX on NX definitely gives the best user experience, though a lack of server software for Windows and Mac make its application outside the Linux lab a bit limited.


NoMachine NX Client
Web: www.nomachine.com

NX connection makes short work of even demanding apps, and plays sound too!

Rating: 8/10

The best Linux remote desktop client: Remmina 10/10

Leaving aside the clients that don't work that well, there's almost a war of ideology going on for the top spots. There's no doubt that NoMachine, although it eschews standard VNC (you can still use it as a VNC client), performs excellently.

In the tests, the OpenGL game was fluid and playable. And while it was fiddly to set up, in use it was better than most. The NX protocol may well be the future, but the client software still has a lot to learn from the user experience guys.

The KDE entry, Krdc, performed well, in spite of its disastrous early start with the companion server. That could really be a problem for the Krdc people, because users will likely use them together and be disappointed with the slow performance. If you're running a KDE desktop and need a simple VNC client though, there's probably no need to search further.

TeamViewer provided an interesting diversion to the main event. It wasn't anywhere near as responsive as the main contenders, while we had concerns about security and the 'phone home' nature of the connection. Having said that, it did layer on extra features.

The NX servers do handle sound, but there are some additional options that could be useful when used in a corporate environment.


The winner, by some distance, was Remmina. Performance was exemplary, but that's not the full story. It had the best feedback and responsiveness of any client, and if you didn't know better, the remote desktop might have been a normal-speed local machine.

More than the performance though, this client had the best mix of features, and a sensible and well thought-out interface. Although it did split into multiple windows, the controls are always accessible.

As well as discovering clients on the network, it has a good way of storing connections, which would still work well if you had to deal with lots of desktops. Support for NX makes this an all-round winner.