This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Tunneling does not seem to work here (newbie)?


On Fri, 15 Oct 2004 savantsaro@cox.net wrote:

> Ok, I think I may have figured out the problem, although I still don't know how to solve it.
> 
> The documentation, advice, FAQs, etc seem to have gotten me confused.
> 
> I suspect I've been doing some of these tasks on the wrong system:
> 
> export DISPLAY(foo)
> changing X11Forward in ssh(foo) files
> etc etc.
> 
> Also, emacs is possibly the worst choice of programs to try to test this with on our server, because apparently, running emacs from a terminal on the server itself DEFAULTS TO TEXT MODE and doesn't create a gui window. In other words, it was acting exactly the same on the server as it was remotely.

use xdpyinfo. this will print information to the console and you'll
instantly notice if it's working or not without having to check for 
a window which may have popped up.

> DISPLAY environment variables have been tweaked to goodness knows what on both the cygwin shell on my local box and on the server, under the Administrator and root accounts.

better remove the tweaks on MacOS again. sshd will set the variables 
after login and resetting them will make forwarding disfunctional 

> Various ssh_config and/or sshd_config files have been created/edited on both the server and the cygwin shell on my local box, all of which somewhere contain "X11Forwarding yes" somewhere in them.

The exact option name differs from ssh client and ssh server configuration. See below.

> Some ssh configuration programs have been run, somewhere.

If ssh allows connections from cygwin to MacOS then the plain ssh configuration
is ok.

> Well, it's not really as disorganized as all that, but it seems that way. I have a pretty good idea of what I've done to what files on what systems. Regardless, it seems a good deal of it was done wrong, not that it seems to have affected anything : X11 forwarding still doesn't work.
> 
> So here's my questions, which hopefully will fix things:
> 
> What environment variables need to be set, on which machines? I've seen probably 4 or 5 different variants on the DISPLAY variable, and have no idea what the "correct" one is or why.

Used terms: 
client: cygwin host where you start ssh and where XWin is running
server: unix host where sshd is running and the X11 client is started 

set DISPLAY to :0.0 on client
do not set DISPLAY on server

make sure DISPLAY is not set in any login scripts on the server.

> What configuration/installation programs need to have been run, on what machines, as what users?
> 
> What files, in what directories, on which machines, need to be edited with the "X11Forwarding no" -> "X11Forwarding yes" change?

set ForwardX11 yes in /etc/ssh/ssh_config or ~/.ssh/config on client
set X11Forwarding yes in /etc/ssh/sshd_config on server

Both settings are default set to "yes" but some distributions may change it
to "no". Instead of explicitly setting them to "yes" just make sure they are 
not set to "no"

> Please note, this is *not* a standard *nix box - the directories I've been referred to so far seem to be wrong, leaving me to guess and "locate" a lot.

I'm not sure where the files are on MacOS X so I can only give you the standard places.
 
> The "host" system is running Mac OSX 10.3 Panther.
> The "client" system is running Windows 2000 Server and cygwin.

bye
	ago
-- 
 Alexander.Gottwald@s1999.tu-chemnitz.de 
 http://www.gotti.org           ICQ: 126018723


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]