I'm not sure where/why I'm failing but... I have /etc/ssh/sshd_conf entery of: X11Forwarding yes (which is the default config, as is everything else) When I try to run X-based programs from another PC's ssh session, I get errors like: cannot connect to X server Can't open display: I'm probably missing some little variable somewhere, but heavens know if I can find it.
On Friday 06 February 2004 02.18, Tom Allison wrote:
I'm not sure where/why I'm failing but...
I have /etc/ssh/sshd_conf entery of: X11Forwarding yes (which is the default config, as is everything else)
When I try to run X-based programs from another PC's ssh session, I get errors like:
cannot connect to X server Can't open display:
I'm probably missing some little variable somewhere, but heavens know if I can find it.
Is the other machine a linux? Are you using ssh -X to log in? It sounds like the programs aren't trying to use ssh based X forwarding but rather regular X connections, this is usually because you didn't use the -X flag to ssh
Anders Johansson wrote:
On Friday 06 February 2004 02.18, Tom Allison wrote:
I'm not sure where/why I'm failing but...
I have /etc/ssh/sshd_conf entery of: X11Forwarding yes (which is the default config, as is everything else)
When I try to run X-based programs from another PC's ssh session, I get errors like:
cannot connect to X server Can't open display:
I'm probably missing some little variable somewhere, but heavens know if I can find it.
Is the other machine a linux? Are you using ssh -X to log in? It sounds like the programs aren't trying to use ssh based X forwarding but rather regular X connections, this is usually because you didn't use the -X flag to ssh
They are both SuSE 90 installations. I am not using 'ssh -X' to login. I'm opening an ssh session to the remote machine and trying to run X based applications from that machine onto my desktop. This was done under Debian by setting the X11Forwarding to yes. Why it isn't working here has me stumped. It should be really easy.
I typically use the following syntax... works perfectly... ssh -X des@192.168.0.110 Once I reach the remote computer I launch an 'xterm &' and build up the interface from there. Be sure to use '-X' not '-x' On Fri, 2004-02-06 at 09:34, Anders Johansson wrote:
On Friday 06 February 2004 03.31, Tom Allison wrote:
They are both SuSE 90 installations. I am not using 'ssh -X' to login.
Then do -- Best regards,
Des Aubery... ============================================================> adTherm Technology --> _///^\\\_ Home of Virtual --> --> _///^\\\_ Thermal Engineering... --> Contact: --> _///^\\\_ o Automotive Heat- --> www.adtherm.com --> _///^\\\_ Transfer Devices --> info@adtherm.com --> _///^\\\_ o Virtual Radiator --> Ph : +66 42 614967 --> _///^\\\_ o CFD --> Fax: +66 42 614967 --> _///^\\\_ o FEA --> Mob: +66 6 8553801 --> _///^\\\_ o Brazing & Furnace --> --> _///^\\\_ o Consultants --> Des Aubery --> _///^\\\_ o Nocolok, CuproBraze --> ============================================================>
What X-client are you running on the PC? I ran afoul of the same issue because I couldn't find a $0 X client for Windows. I gave up on that and went to VNC (www.realvnc.com), which is freely available for both Linux and Windows. As I type this, I am running Evolution on my Linux, accessed through a Netscape web browser pointing to my VNC service on Linux. This requires opening a few ports on your Linux server. The download you get from Cambridge is very complete in its documentation. Even I had little trouble getting it running. On Thu, 2004-02-05 at 20:18, Tom Allison wrote:
I'm not sure where/why I'm failing but...
I have /etc/ssh/sshd_conf entery of: X11Forwarding yes (which is the default config, as is everything else)
When I try to run X-based programs from another PC's ssh session, I get errors like:
cannot connect to X server Can't open display:
I'm probably missing some little variable somewhere, but heavens know if I can find it. -- Daryl Lee Open the Present, it's a Gift.
On Friday 06 February 2004 02.39, Daryl Lee wrote:
What X-client are you running on the PC? I ran afoul of the same issue because I couldn't find a $0 X client for Windows.
terminology alert: an X client is a program that displays its things using X. xclock is an x client and so is evolution. What you (probably) were looking for was a $0 X server for windows, which can be found in the cygwin project at http://www.cygwin.com
What X-client are you running on the PC? I ran afoul of the same issue because I couldn't find a $0 X client for Windows. I gave up on that and went to VNC (www.realvnc.com), which is freely available for both Linux and Windows. As I type this, I am running Evolution on my Linux, accessed through a Netscape web browser pointing to my VNC service on Linux. This requires opening a few ports on your Linux server. The download you get from Cambridge is very complete in its documentation. Even I had little trouble getting it running. On Thu, 2004-02-05 at 20:18, Tom Allison wrote:
I'm not sure where/why I'm failing but...
I have /etc/ssh/sshd_conf entery of: X11Forwarding yes (which is the default config, as is everything else)
When I try to run X-based programs from another PC's ssh session, I get errors like:
cannot connect to X server Can't open display:
I'm probably missing some little variable somewhere, but heavens know if I can find it. -- Daryl Lee Open the Present, it's a Gift.
On Friday 06 February 2004 12:18, Tom Allison wrote:
I have /etc/ssh/sshd_conf entery of: X11Forwarding yes (which is the default config, as is everything else)
When I try to run X-based programs from another PC's ssh session, I get errors like:
cannot connect to X server Can't open display:
The setting that stops you is on the client side. On those workstation Suse 9.0 boxes edit /etc/ssh/ssd_config to finish with host * ForwardX11 yes THAT'S the one that isn't yes by default. michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166
Michael James
The setting that stops you is on the client side. On those workstation Suse 9.0 boxes edit /etc/ssh/ssh_config to finish with
host * ForwardX11 yes
THAT'S the one that isn't yes by default.
It's safer to keep the default and use the -X option only for computers that are "trusted". -- A.M.
Alexandr Malusek wrote:
Michael James
writes: The setting that stops you is on the client side. On those workstation Suse 9.0 boxes edit /etc/ssh/ssh_config to finish with
host * ForwardX11 yes
THAT'S the one that isn't yes by default.
It's safer to keep the default and use the -X option only for computers that are "trusted".
-- A.M.
I solved this by using the sshd_config setting to ForwardX11 yes I really don't see how this can be any less safe since at this point you have already established an ssh connection to the machine. Unless there is something about running X that isn't pretected by ssh tunneling or worse. The worst I've found is that not all applications (Mozilla) will work correctly when running on a client+server that are not of the same machine. But it was no less secure. Regardless of all the security issues, this is all in a protected environment of sorts. I use ssh to contact my DMZ servers and would like to set them up headless. My next question is how to set up a remote X login to a DMZ server running through X.
participants (6)
-
Alexandr Malusek
-
Anders Johansson
-
Daryl Lee
-
Des Aubery
-
Michael James
-
Tom Allison