On Fri, 12 Apr 2002, Ward William E DLDN wrote: > Nope; it doesn't "just work". Of course, maybe > if I gave a better picture of the situation..... > > Trying to connect to a machine (Rizzo) which is > outside the firewall. SSH is running, and the > sshd_config is set to allow Xforwarding. I just > set it, and even rebooted the sshd demon to make > sure it picked it up. > > Firewall allows the port 22 connection out. I > am running on the desktop a (I know!) Windows NT > box with Exceed as my X server; I use PuTTY to get > out. > > Login to the box via SSH is fine. Environment shows > the SSH client and the "remote host" but both point > to the Firewall (of course; it's doing NAT). So, > I try to do an Xload; nada, I get the standard > "Error: Can't open display:" message which tells me > I need to set the display environment variable. > > So, how do I the X Windows through the SSH pipe? >
We do this (but not through a firewall) using Tera Term Pro and SSH Secure Shell as the Windows SSH clients, and XWin-32 as the Windows X server. The first thing we do is start the X server, running in the background. That is, the X server starts but is not configured to connect to anything. We then start the SSH client (configured to do port forwarding) and log in via SSH to a Unix box whose SSH daemon has been configured to forward the X protocol. At this point, the user has $DISPLAY defined to be an SSH-forwarded port on the PC. When you see the message: Error: Can't open display: it means that SSH isn't getting the X forwarding done correctly. That has meant for us either: - the SSH client isn't configured for port forwarding, or - the desktop X server isn't running. Carl Carl G. Riches Software Engineer Department of Mathematics Box 354350 voice: 206-543-5082 or 206-616-3636 University of Washington fax: 206-543-0397 Seattle, WA 98195-4350 internet: [EMAIL PROTECTED] > > -----Original Message----- > > From: David Talkington [mailto:[EMAIL PROTECTED]] > > Sent: Friday, April 12, 2002 3:52 PM > > To: Redhat-List (E-mail) > > Subject: Re: Tunnelling X through ssh > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Ward William E DLDN wrote: > > > > >Anyone know how to tunnel X through SSH? > > > > > >I want to setup a secure ssh connection and display > > >my X results back on the original; I have a firewall > > >that blocks everything except port 22, so I need to > > >tunnel on the connection proper. Any clues, short > > >of a VPN? > > > > You don't have to do anything special at all, as long as X > > forwarding is > > enabled on both client and server (ssh_config, sshd_config), > > and there's > > an X server running on the client end. > > > > It "just works". > > > > - -d > > > > > > - -- > > David Talkington > > > > PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp > > > > -----BEGIN PGP SIGNATURE----- > > Version: PGP 6.5.8 > > Comment: Made with pgp4pine 1.75-6 > > > > iQA/AwUBPLc6yr9BpdPKTBGtEQIBGACgt+aG7VikaxAaAOU+BuhihNFbiywAn0Dc > > IG6WmeF/0kiST6lZEsRtWpm2 > > =05F0 > > -----END PGP SIGNATURE----- > > > > > > > > > > _______________________________________________ > > Redhat-list mailing list > > [EMAIL PROTECTED] > > https://listman.redhat.com/mailman/listinfo/redhat-list > > > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
