Remote Desktop Options for Linux

Ask any long-term Linux enthusiast, and they'll be the first to tell you there isn't much you can do with another operating system that you can’t do with Linux. Oh sure, there are always going to be those legacy applications that some may people depend on. For the most part though, everything you need is readily accessible with today's modern Linux distros.

One of my favorite examples of desktop Linux readiness is the various options available to control a computer remotely. Despite what newer Linux users might think, there are indeed a number of open source and closed source options available for remote PC access. In this article, I'll be exploring the best of both options from each sector of software licensing.

Vinagre (VNC based): My go-to application for running local VNC based connections tends to be Vinagre. It's simple and it provides a very consistent experience on the GNOME desktop. Some of the best features of using Vinagre include the following.

• Connect to multiple PCs at once. If you're bouncing between computers, this is can be very helpful.
• Vinagre remembers your last connection(s). Forget about looking up the last machine you connected to, let Vinagre do it for you.
• Browsing for PCs made easy thanks to the network discovery options.
• GNOME keyring compatible; no more entering your password each and every time.
• Accepts reverse connections. This is helpful when offering remote support on your LAN or when you're behind a firewall.
• With SSH setup ready to go, you can also use a terminal window to run Vinagre with SSH.

KRDC (VNC/RDP based): Next up, we have a great KDE application that mirrors the same functionality as Vinagre. The great thing is that KRDC feels very natural to anyone who has used Vinagre previously. The features of KRDC include the following.

• Connect to multiple PCs at once. KRDC supports this very nicely.
• Remembering your previous connections. The easiest approach is to use the bookmark option for KRDC.
• Very simple access to network browsing. If there are PCs with the right VNC port open, KRDC will see them and allow you to connect.
• Use SSH, to connect to other PCs securely with a terminal and KRDC.

For those of you wanting more from your remote control applications, the Linux desktop delivers here as well. Below you’ll find more advanced solutions that offer greater functionality for the more advanced enthusiast.

Remmina (RDP, VNC, NX, XDMCP, SSH, Telepathy based): Widely considered to be the go-to remote application among many Linux users, Remmina offers support for a multitude of remote access protocols. This GTK based application also has the slickest support for SSH, because it's built very tightly, right into the application. Features that Remmina offers include the following.

• A tabbed user interface. This is handy for keeping track of everything.
• A smart tray icon, which makes switching from one connection to another a simple endeavor.
• Provides smooth controls for SSH integration. Just select VNC, then tab over to SSH and setup accordingly.
• Offers a floating toolbar when in full screen. This is helpful, when you're working with limited screen real estate.
• With server settings manually setup, the listing for each is easily accessible.

SSH with X11 Forwarding (SSH): Over the years, I've come to use SSH with X11 forwarding less than I once did. Not because there is anything wrong with it, rather because my own personal needs have been largely met by merely using other clients. That said, there is something inherently fascinating about running this software program. The features of using this option are as follows.

• You can run many programs such as FTP, email and other software from other PCs as if it was run locally. For example, you can use SSH with X11 forwarding to run xclock on the remote PC, but it will visually appear as it was run locally. This is a great way to access specific applications remotely, without accessing the entire remote desktop.
• With compression enabled, this option can provide a better user experience than merely running access to the remote desktop. Since it's only a single application being accessed, the bandwidth may be less likely to bottleneck on you.