Re: xwinclip authorisation problem with remote hosts using XDMCP

["Matthew Donald" <matthew dot donald at motile dot net>]

----- Original Message -----
From: "Alexander Gottwald" <alexander.gottwald@informatik.tu-chemnitz.de>
Cc: <cygwin-xfree@cygwin.com>
Sent: Tuesday, January 15, 2002 7:08 PM
Subject: Re: xwinclip authorisation problem with remote hosts using XDMCP


> This is wrong. 127.0.0.1 is the ip adress for localhost. On every
computer,
> 127.0.0.1 points to itself. Say you have a windows host with ip
192.168.26.201
> and a unix host with ip 192.168.26.202, they can only communicate with
these
> ip adresses. Connecting 127.0.0.1 from the windows host will connect to
the
> windows host and connecting 127.0.0.1 from the unix host will connect to
the
> unix host.
>
> The correct way is to run xhost windows.host.ip and xwinclip -display
> windows.host.ip:0

I use 127.0.0.1 instead of localhost or windows.host.ip because I can't
guarentee that
these names will be defined.  While I agree that 127.0.0.1 is inelegant, it
has the advantage
that it will always work even if the PC is configured with a broken host
file and DNS is
not configured.

Running 'xhost +127.0.0.1' (or 'xhost +localhost') results in an X access
error, as I
explained previously

>
> >
> > to 127.0.0.1:3.0 broken
>
> Why are you connecting to display 3? this should be 127.0.0.1:0

Sorry, the ':3' was a typo.

regards Matthew.