David Timms wrote:
> Mikkel L. Ellertson wrote:
>> David Timms wrote:
>> If xclock runs, then it has all the libraries it needs.
> No, it doesn't run on the cut down machine it doesn't have Xserver
> installed, and is running text mode.
>
It runs - you would not get the can not connect error message if it
didn't. You would get a missing library message.
>> But unless
>> you made a typo, it is really strange that you set DISPLAY to
>> 192.168.0.201:0 and the error is about trying to connect to
>> 192.168.32.101:0.0. That is not even in the same subnet.
> Correct. I made a typo when entering this query, sorry to confuse.
>
>> I strongly recommend using "ssh -Y" to tunnel the connection between
>> machines, as it is more secure.
> Machine is cut down no ssh yet!
>
Unless you are really strapped for space, it is worth having. It
does not take that much space/resources.
>> It also eleminates needing to run
>> xhost +192.168.0.99 and set DISPLAY. But if you are going to do it
>> this way, try running "xclock -display 192.168.0.201:0" and see what
>> that shows.
> Error: can't open display: 192.168.32.201:0
>
> {xserver is on 192.168.32.201, the cut down pachine is 192.168.32.99
> If that works, we can then work on what is going wrong
>> when you try and set DISPLAY.
>
> OK, trying with ssh:
> $ ssh -Y 192.168.32.99
> Last login: Sat Aug 11 03:23:32 2007 from 192.168.32.201
> $ xclock
> Error: Can't open display:
In /etc/sshd/sshd_config on 192.168.32.99, make sure you have:
X11Forwarding yes
If not, add it and restart sshd.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
