Date: Sun, 4 Apr 2004 21:07:43 +0200 (CEST) From: Cordula's Web <cpghost@cordula.ws> To: jcm@FreeBSD-uk.eu.org Cc: freebsd-questions@freebsd.org Subject: Re: remote X display Message-ID: <20040404190743.B589940811@fw.farid-hajji.net> In-Reply-To: <20040404141521.GA57803@dogma.freebsd-uk.eu.org> (message from Jonathon McKitrick on Sun, 4 Apr 2004 15:15:21 %2B0100) References: <20040122145353.GB54084@dogma.freebsd-uk.eu.org> <20040404141521.GA57803@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> : somehost> ssh -X user@remotemachine > : remotemachine> echo $DISPLAY > : somehost.example.com:10.0 > : remotemachine> xclock & > : > : Don't forget to enable X forwarding in /etc/ssh/sshd_config: > : X11Forwarding yes > > I had this working before, but I'm having problems. My main box is missing > a monitor (on repair). Would that make a difference? Will X apps run on the > main box without a monitor and forward X to the remote client? > > Right now, I get this: > neptune:~> echo $DISPLAY > > neptune:~> If DISPLAY is not set, then ssh on your local machine and sshd on the remote box didn't establish an X11 forwarding channel. Are you sure that sshd_config is set up properly on the remote machine? Did you use -X (that's uppercase X) while invoking ssh locally? Perhaps your local ssh and remote sshd are not talking the same version of the SSH protocol? BTW, it is irrelevant if the remote box has a monitor or not. That box doesn't even need an X server (wether running or not). Only X clients and X libraries are needed on the remote machine. -- Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040404190743.B589940811>