From mike@boobaz.net Thu Nov 9 14:18:45 2000 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA217778 for ; Thu, 9 Nov 2000 14:18:43 -0800 Received: from boobaz.net (c1056043-a.sttln1.wa.home.com [24.19.193.36]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA02070 for ; Thu, 9 Nov 2000 14:18:43 -0800 Received: from c1056043-a (c1056043-a [24.19.193.36]) by boobaz.net (8.9.3/8.9.3) with ESMTP id OAA10056 for ; Thu, 9 Nov 2000 14:18:42 -0800 Date: Thu, 9 Nov 2000 14:18:42 -0800 (PST) From: Mike X-Sender: mike@c1056043-a.sttln1.wa.home.com To: UW Linux Group Subject: Re: [OT] XConfused (Was: DISPLAY variable and ssh) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In Linux (which you should install and use...frequently) there is client-based access control you need to worry about. On the Linux side you'd use a tool like 'xhost' to specify which remote hosts can connect to your X server. Is there a similar access control on the Windows X servers? (I dunno) --------------------------- -=<(| mike@boobaz.net |)>=- On Thu, 9 Nov 2000 at 14:03, William Rowden wrote: |Since I use TTSSH, after reading this thread I tried to use it to |"[d]isplay remote X applications on [my] local X server." It's not |working, so I hope someone can suggest where to begin fixing it. |There's no "XWindows for Dummies" mailing list, so my message is |here, though off-topic. | |Here's the problem: when I try to run a client (e.g., |/usr/X11/bin/xterm at my ISP) I get an error: | | X connection to eskimo:20.0 broken (explicit kill or server | shutdown). | |ISTR receiving this error in Linux when the DISPLAY wasn't set |correctly. However, ssh set the display: | | DISPLAY=eskimo:20.0 | |(This is an example; it's different for each shell, since I don't |set DISPLAY in my .*cshrc.) | |I've successfully forwarded the ports for http, nntp, smtp, pop3, |etc. to my local machine; it's just X that doesn't yet work. The |results are the same whether I use WeirdX or MI/X on my local |Windoze NT 4.0 box. (If I could install Linux at work--where I have |enough bandwidth for X--as well as at home, I wouldn't have this |problem, I suppose.) | |Does anyone have a suggestion? Setting the display to work outside |of the ssh channel (e.g., /usr/X11/bin xterm -display XXX.XX.XXX.XX) |doesn't work, either, but that's probably because the NT box is |behind a firewall: | | Error: Can't open display: XXX.XX.XXX.XX | |If the detail matters, I'm using Tera Term Pro version 2.3, with |TTSSH 1.4 for X Tunneling. |-- | -William |PGP key: http://www.eskimo.com/~rowdenw/pgp/rowdenw.asc until 2001-02-01 |Fingerprint: B6E5 9732 3464 97C8 2B70 A031 6BF6 9E5C 16B5 C4000 |Muff Potter's my friend. And when a friend's in trouble, you can't run away. | | | | | | | | | | | |-- | -William |PGP key: http://www.eskimo.com/~rowdenw/pgp/rowdenw.asc until 2001-02-01 |Fingerprint: B6E5 9732 3464 97C8 2B70 A031 6BF6 9E5C 16B5 C4000 |I'll be back! | | | | | | .