Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: ejfried AT ca DOT sandia DOT gov (friedman_hill ernest j) Message-Id: <200301271751.JAA13627@ca.sandia.gov> Subject: Re: ssh x forwarding In-Reply-To: <4165C48DE9A0D211B6400800095C585F172F02@WASHINGTON> from Patrick Nelson at "Jan 27, 2003 09:44:07 am" To: cygwin AT cygwin DOT com Date: Mon, 27 Jan 2003 09:51:57 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Not that this is sure to solve your problem, but it's a possibility: ssh daemons can be configured to prohibit X forwarding. Try ssh -v -l to see what ssh reports regarding whether X forwarding was actually established, and/or check the sshd_config file on the remote machine (if you have permission; otherwise, ask the admin.) I think Patrick Nelson wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] > In ssh you get x forwarding. But, I can't seem to get it working. A > command like: > > ssh -l > > always responds with something like: > > Gtk-WARNING **: cannot open display: > > Is there some configuration that needs to take place in cygwin first? Yes I > can log in by dropping the part and yes the is available. > Tried running the above from a terminal that displayed after doing a > "startx" too... same result. So I have to figure I just don't have > something setup correctly. > --------------------------------------------------------- Ernest Friedman-Hill Distributed Systems Research Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 ejfried AT ca DOT sandia DOT gov Livermore, CA 94550 http://herzberg.ca.sandia.gov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/