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: "Todd Bowden" To: Subject: RE: Can't get ssh to forward X packets Date: Fri, 11 Jul 2003 15:13:34 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <20030711200802.11474.qmail@web20418.mail.yahoo.com> Jeff, I too ran into this problem and finally found the answer. SecureCRT is probably doing the samething your doing and that is setting the DISPLAY before ssh'ing to your system. You can also use PuTTy which I truly love. I can do anything with PuTTy that I can with SecureCRT and its Free. Todd C. Bowden HP Certified AtosOrigin 5000 S. Bowen Arlington, TX 76017 Office: 817-264-8211 E-mail: Todd DOT Bowden AT atosorigin DOT com -----Original Message----- From: Jeff Nokes [mailto:jeff_nokes AT yahoo DOT com] Sent: Friday, July 11, 2003 3:08 PM To: Todd Bowden; cygwin AT cygwin DOT com Subject: RE: Can't get ssh to forward X packets Thanks for the reply Todd. Here's what I found: Before changing anything: - There was still no $DISPLAY set on the remote host after logging in. No change in behavior, X still not forwarding. After setting a local DISPLAY in my Cygwin ennvironment, I then tried the follwoing, and it worked, but I did get an xauth data warning: jnokes AT D-SJC-JNOKES ~ $ ssh -X jnokes AT row-cm Warning: No xauth data; using fake authentication data for X11 forwarding. [jnokes AT row-cm jnokes]$ echo $DISPLAY localhost:10.0 [jnokes AT row-cm jnokes]$ - I ran a test with xeyes and it worked fine. Thanks for the solution. I'm now intrigued as to why I needed this, never have in the past, and it alwyas just worked fine. And what is SecureCRT doing "under-the-hood" to make it work without any visible warnings that Cygwin ssh is not doing? Thanks again for the help. - Jeff --- Todd Bowden wrote: > The problem is on the client side. > > Before you ssh to your other systems export DISPLAY=localhost:0 > > Than try and ssh into Linux systems. > > Test: > 1. Before changing anything ssh into Linux system. What does > $DISPLAY say? 2. After changing display on client side, What does > $DISPLAY say? > > Todd C. Bowden > HP Certified > AtosOrigin > 5000 S. Bowen > Arlington, TX 76017 > Office: 817-264-8211 > E-mail: Todd DOT Bowden AT atosorigin DOT com > > > -----Original Message----- > From: Jeff Nokes [mailto:jeff_nokes AT yahoo DOT com] > Sent: Friday, July 11, 2003 2:41 PM > To: cygwin AT cygwin DOT com > Subject: Can't get ssh to forward X packets > > > Hi, > My name is Jeff. I recently started a new job that gave me a Win2K > box to ssh into the various unix environments to do my work. The box > came with SecureCRT on it, and it works fine. I prefer to use the > cygwin environment so I set it up on my workstation, and it seems to > work fine as well, except for two issues, one of which is the question > of this posting. > > Whenever I ssh into my dev linux boxes, wishing to have X packets > forwarded back to my local Xserver on my workstation, it doesn't seem > to be working through ssh on Cygwin. It does, however, work with > SecureCRT. I just set up Cygwin in June, so all the packages are > up-2-date. And I've been using it for a long time at other jobs, and > at home, and the X forwarding via ssh always works, but not this time. > I've even tried re-installing the ssh package, but no changes. When > looking at the verbose output, no mention of X forwarding at all. I > know I'm doing it correctly: > ssh -X username AT host > ... and I do log in successfully, but there's never a $DISPLAY > variable set on the remote host, as there should be. When I check > $DISPLAY when logging in with SecureCRT, I can see it just fine, and X > forwards perfectly. So, the OpenSSH server is not the issue. I've > even tried setting my ~/.ssh/config file to have 'ForwardX11 yes', > still nothing. I've tried it using interactive and passive logins, > etc., still no change. > > The older versions of Cygwin I've ran in the past always forwarded X > seamlessly, not sure why the most recent install won't. Anyone have > any ideas? > > Thanks in advance, > - Jeff > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/