Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have two computers both running Debian (testing). The host PC has ssh installed and running, I'm using Putty on the client PC to make the ssh connection. I have no problems making the ssh connection and logging into the host with Putty, but when I try to run an application (gimp for instance) I'm getting the following message:
The application 'gimp' lost its connection to the display localhost:10.0;
Most likely the X server was shut down or you killed/destroyed the application.
PuTTY can establish the ssh connection with tunneling. However, PuTTY is NOT an "X Client". You have to run something else on your M$ Windoze machine to actually see the X windows.
eXceed from Hummingbird (my favorite - been using its various versions for years)
Non-Commercial ("free") Product
xming - Built out of the Cygwin stuff
Seems to do OK but since I had eXceed before I got it I haven't really beaten on it. My co-worker has indicated there are some color/font issues he has seen but everything I did with it seemed to work OK.
Exactly HOW are you running PuTTY? I'm wondering if you're not doing some sort of DOS/Windows emulations (WINE or something like that) and running PuTTY in that environment. So far as I know there is no "PuTTY" port to install directly in Linux because its avowed purpose to allow Windoze machines to do telnet/ssh connections to UNIX/Linux machines.
Are you actually IN a GUI environent? If you open a "terminal" window (NOT PuTTY and not connected to remote side - just locally) and just type "xterm" does it open and xterm window on your screen?
My apologies. I'm now downloading the FC4 package using yum.
I'll see if it operates any differently than the one on my company provided Windoze machine and report back.
Make sure you don't have anything on the remote end that is explicitly setting the "DISPLAY" variable. The tunnel creates its own DISPLAY setting and you must use that rather than standard DISPLAY setting method to use the tunnel.
It isn't unsusual to have DISPLAY=<whatever>.#.# in one of your start up files (/etc/profile, /etc/bashrc, $HOME/.profile, $HOME/.bashrc) when you login. If you do that would overwrite the one that the tunnel is setting.
Also make sure you're not doing an "su - <user>" AFTER you open the tunnel. That would lose the DISPLAY variable as well.
OK I just did my test to a system where we purposefully block 6000 range ports because it is web facing. That is an HP-UX (UNIX) 11.11 host.
I was able to open a PuTTY session from Fedora Core 4 (FC4) to the HP-UX host successfully with X tunneling. I then ran "xterm" in that established window and it successfully sent the Xterm window back to my Gnome display on the my FC4 console.
Although the PuTTY on FC4 had some additional options not seen on the Windoze PuTTY I'd downloaded (may be time to update that) I didn't use any of those newer options. What I did use:
Under the "Tunnels"
Checked the box for "Enable X11 forwarding".
Kept the default selection for "MIT-Magic-Cookie-1"
Kept the default selection for "Local"
Did not select anything else or type anything in the boxes on that.
In the main Session window I had the host IP and selected ssh and let it use port 22 (default for ssh). I saved it with the host name then used this session. As noted it opened fine and successfully opened the tunnel which successfully sent the X application back to my originating FC4 box.