TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TCLUG:12255] X
Well, here's the skinny. Box A is a RH6.1. Box B is a MacOS 8. I'm using MI/X
on B to display apps running on box A.
Obviously this limits me in certain ways, as I do not have all the options
available at all times, due to not having an actual linux distribution on B.
The simple instructions I have mostly say :
"Set the environment variable on A to point to B. Run the App on A, and it
should display on B. If it doesn't, your outta luck..."
Brian
----------
>From: Hans Davin Umhoefer <spudling@acm.cs.umn.edu>
>To: tclug-list@mn-linux.org
>Subject: Re: [TCLUG:12255] X
>Date: Wed, Jan 12, 2000, 5:04 PM
>
>
> If you have X at both locations you should be able to use ssh's X
> forwarding to make things real simple. SSH automatically forwards your X
> display.
>
> Barring that, you should be able to do this by issuing the command
>
> xhost +hostname_or_ip_of_box_B
>
> on box A. This will allow box B to forward it's display to box A. This
> method may not work through your firewall (I've never tried it) but SSH
> definitly should.
>
> Hope this helps to narrow down the problem.
>
> Hans
>
>
> Brian Ackermann wrote:
>> Does anyone know of a way to test whether or not X can make it between points
A
>> and B?
>>
>> I'm working on a program from a remote box A, and I have MI/X at box B.
>>
>> issuing the following command gives:
>> ====
>> [root@nic-31 .vnc]# xclock -d 144.15.8.165:0.0&
>> [1] 1263
>> [root@nic-31 .vnc]# Error: Can't open display:
>> [1]+ Exit 1 xclock -d 144.15.8.165:0.0
>> [root@nic-31 .vnc]#
>> ====
>> also, doing
>> ====
>> [root@nic-31 .vnc]# export DISPLAY=144.15.8.165:0.0
>> [root@nic-31-c29-111 .vnc]# xclock&
>> [1] 1267
>> [root@nic-31-c29-111 .vnc]# _X11TransSocketINETConnect: Can't connect: errno
= 1
>> 13
>> Error: Can't open display: 144.15.8.165:0.0
>> [1]+ Exit 1 xclock
>> ====
>> both methods give errors, so I'm assuming that either
>>
>> 1) I've messed something up.
>>
>> -or-
>>
>> 2) The firewall I'm behind currently won't let X through
>>
>> Either is quite possible..
>>
>> Is there a way to assure that 2 is the cause?
>>
>> Thanks in advance,
>>
>> Brian
>>
>
> --
> Hans D Umhoefer (spudling@acm.cs.umn.edu)
> --
> Finger spudling@154-233.dsl.scc.net for my public pgp key.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
>
>