I have an Ubuntu server running on EC2 (which I didn't install myself, just picked up an AMI). So far I'm using putty to work with it, but I am wondering how to work on it with GUI tools (I'm not familiar with Linux UI tools, but I want to learn). Silly me, I'm missing the convenience of Windows Explorer.

I currently have only Windows at home. How do I set up GUI tools to work with a remote server? Should I even do this, or should I stick to the command line? Do the answers change if I have a local linux machine to play with?

  • If X11 forwarding is fast enough (there are cases where it's not) it should be fine. The CLI is always more powerful so it's useful to not ignore it but this doesn't mean that GUIs are never useful :)
    – sakisk
    Commented Mar 22, 2011 at 8:26
  • But what kind of tasks do you want to fulfil on the server? Which tools do you want to use? It's important information for an answer. Say, you mentioned something called "Windows Explorer"; but there's probably no "Windows Explorer" on Ubuntu, so the solution suggesting running some X programs remotely won't fit. Commented Mar 22, 2011 at 9:11
  • There is no Explorer equivalent for Ubuntu? Seriously?
    – ripper234
    Commented Mar 22, 2011 at 9:22
  • 1
    @imz - currently I'm interested in the general problem. I'm not experieniced with linux GUI apps at all, so I have no idea what I want right now... the first use that comes to mind is navigating folders in an Explorer like fashion, and perhaps editing.
    – ripper234
    Commented Mar 22, 2011 at 10:23
  • 1
    @ripper234: For navigating directories, check out mc. Commented Mar 22, 2011 at 16:14

8 Answers 8


You can use X11 forwarding over SSH; make sure the option

X11Forwarding yes

is enabled in /etc/ssh/sshd_config on the remote server, and either enable X11 forwarding by hand with

ssh -X remoteserver

or add a line saying

ForwardX11 yes

to the relevant host entry in ~/.ssh/config

Of course, that requires a working X display at the local end, so if you're using Windows you're going to have to install something like XMing, then set up X11 forwarding in PuTTY as demonstrated in these references:

ETA: Reading again and seeing your clarifications in the comments, FTP might suit your needs even better, as it will let you 'mount' SFTP folders as if they're regular network drives.  See here, here, here (for Windows XP/7/Vista), or here (for Windows 8).


Shadur covered how to enable X. Note that the /etc/ssh/sshd_config is at the server end, and the ~/.ssh/config is at the client end, so we are in general talking about two different machines. X forwarding will display your remote application on the local X display. So the two configs have to tell the remote and the local to allow this operation to happen, respectively.

As to whether you should use X, it depends. You need to consider (at least) the following factors.

  • What kind of bandwidth do you have? What is its speed? Is it metered? Is there a cap? If you have a very fast connection to the net and no restrictions, that X is more usable, otherwise it can be very slow. Bear in mind that in general X is a network hog; it is not bandwidth optimized (or whatever the right phrase is).

  • What tools are you planning to use over X? Are there non-gui replacements/equivalents? If you give examples of the kinds of tools you are thinking of using, people could suggest alternatives if available. Also be aware that some well known tools come in both gui and commandline/console form. Eg. emacs, aptitude, reportbug.

In general my recommendation is to use command line (apt, wget, rsync) or curses applications (like aptitude or mc) if they are available and do what you need. Such apps aren't necessarily worse than X apps; some of these are fine applications. Eg. The software of John Davis, eg jed and slrn, both console apps, show his distinctive aesthetic, and are works of art. BTW, running a X server on a Windows client to connect to a Linux server is an option, though not a particularly good one.

If you have a local linux server, then the bandwidth issues go away, and X is a much more viable option.

  • I concur that unless you're working over a fairly fast (low latency being slightly more important than bandwidth) link it's generally a better idea to use command-line tools if they're available. Commented Mar 22, 2011 at 8:52
  • 1
    @Shadur - my latency isn't great event on the command line, perhaps I should not even attempt a UI tool because it will probably be too slow.
    – ripper234
    Commented Mar 22, 2011 at 10:25

I have found freenx and nxclient to be a very high-performance remote desktop solution, far better than vnc or X11. I would give that a try.


You should consider sticking to the command line, because a) most servers dont even have a GUI installed, and b) all GUIs are kind of slow to use over networks.

That said, I would suggest having a look at VNC. There are native clients for Windows and servers for Linux, so you would not have to set up X11 on your Windows box.


If you used Emacs, you could run a locally installed Emacs on your Windows, and do file editing, file&directory management (dired), version control, compilation, and also some other random work in the shell (M-xshell or M-xeshell), and probably some more things via TRAMP in your local Emacs. (Some easily findable demo videos that perhaps can make a person not so scared of the unknown Emacs, and TRAMP, etc.: 1, 2.)

That's an illustration that remote X programs might not be the right solution for you. In contrast to the remote X clients way, the TRAMP way involves no heavyweight "graphical" traffic over the remote connection, it uses the ssh connection only to send directory listings, files, and command output back and forth.

Say, if you want to work with "Windows Explorer", then there still won't be a "Windows Explorer" on the Ubuntu server, so you can't run it remotely.

But if "Windows Explorer" had something like TRAMP as a feature (for remote accesses via SSH), you could continue to happily use your local "Windows Explorer", if that's all what you need.

  • He's asking about GUI tools, not a GUI editor for config files. [xkcd.com/378/] aside, Emacs isn't the answer for everything, and in this case you come across as wielding a hammer just looking for a way to describe the problem as a nail. Commented Mar 22, 2011 at 9:22
  • @Shadur: (Me laughing.) He hasn't yet specified what kind of tools he needs. GUI Editor is also a GUI tool, isn't it? Or do you have a special understanding of what a "tool" is? Commented Mar 22, 2011 at 9:26
  • @Shadur BTW, the point of my answer is to suggest a potential approach to a solution that would match his demands as precisely as possible, without us knowing exactly what tasks he wants to solve. My logic is: 1) he likes "Windows Explorer" 2) we don't know which features of "Windows Explorer" he likes because he hasn't specified this. ==> So, if "Windows Explorer" had something like TRAMP, that would be a kind of ideal solution and answer: the features he likes are there, and it would work with his remote server. Commented Mar 22, 2011 at 10:04
  • Is my answer irrelevant for this question?.. :) No, I don't think so, because ripper234 is looking for ideas -- (s)he writes "Should I even do this, or should I stick to command line?" And that's a new idea: look for TRAMP-like solutions, too. That's similar to my personal experience: when I wondered about a convenient way to work on a remote server, a friend of mine said IIRC that he is happy to use TRAMP in Emacs; and I started considering this as an option, too. Commented Mar 22, 2011 at 10:17
  • 1
    And I occasionally use the equivalent in gedit via the ssh/sftp backends for gnome-vfs. Again, "a way to use a GUI editor to change config files on a remote system" is a different question from "using GUI administration frontends remotely" Commented Mar 22, 2011 at 11:45

Unlike RDP, X loses the session if the server or ssh tunnel disconnects. You can use XVNC, which presents an X server to the client programs and connects to a VNC client. This keeps the X session alive and allows you to connect abd disconnect the VNC session.

I've had it working successfully over a 128k/128k Jetstart DSL connection (Yes, Telecom NZ really used to offer a 128k/128k DSL service!). It was fairly reponsive, only slowing down when it had to download a large bitmap to the VNC client.

You can see how to tunnel VNC over ssh in this article.


I use nautilus --no-desktop on Ubuntu server 11.04 for MS Windows Explorer type functionality.

  • How does this help with remote access? Commented Mar 29, 2019 at 17:57

I did find the gvfs-tree command, or in some flavors of Linux just tree, to be helpful in seeing a CLI representation of the directory tree.

  • 2
    Welcome to U&L! I'll fix up the formatting of your answer after this, but I'll point out that while gvfs-tree and tree may be useful commands, how do they address this question's point of "How do I set up GUI tools to work with a remote server?" ?
    – Jeff Schaller
    Commented Sep 23, 2018 at 14:55
  • His post had several questions, ("I'm not familiar with Linux UI tools, but I want to learn" and "Should I even do this, or should I stick to the command line? ").) I thought that making him aware of the gvfs-tree command might make him more comfortable in the CLI, which would make a gui less necessary.
    – jkm
    Commented Sep 23, 2018 at 15:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .