This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Can't remote connect to XF86 on Win2K


Exactly. If I use -indirect I can't even make local connections to the X
server - they just seem to hang. Becaue of this I can't do a 'xhost +'
to allow connection from a remote process. So it seems I have to get the
cookie correct. Unfortunately, your explaination lost me a little. Do I
have to generate a cookie, or should a cookie have been sent as part of
the XDMCP connection? Why would it work fine on Win95/98 and not Win2k?

Seems to be and FAQ on Win2k this one, but I can't find an answer.

Thanks,
Nick.

On Sun, 2002-06-23 at 17:57, Alexander Gottwald wrote:
    On 21 Jun 2002, Nick THOMPSON wrote:
    
    > 'xhost +' seems to take a long time and has no effect. Trying indirect
    > XDMCP with another remote machine logs the following on the remote:
    
    Wgat do you mean with "indirect XDMCP"?
    Did you start the server with XWin -indirect login.server.name?
    
    > Xlib: connection to "myhost:0.0" refused by server
    > Xlib: Invalid MIT-MAGIC-COOKIE-1 key
    > Error: Can't open display: myhost:0
    
    The server wants the correct cookie which was set via XDMCP. On the
    X-Terminal the cookie should be set.
    
    try "xauth list $DISPLAY"
    
    On any other machine you have to set it manually via "xauth add"
    or use ssh -X to pass the cookie to the remote machine.
    
    bye
        ago
    -- 
     Alexander.Gottwald@informatik.tu-chemnitz.de
     http://www.gotti.org           ICQ: 126018723



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]