Harvey,

Thanks for suggesting the "ssh -Y".  That works (as done "ssh -X") but unfortunately it doesn't solve my problem. We are trying to drop X2Go into an existing environment as a replacement for a current solution, and can't force a change in how users connect to the remote machines. For X2Go we really need to figure out how to get this working with a simple "xhost +" and "setenv DISPLAY host:display".

Interestingly, it looks like freenx/opennx work fine in this mode, but we would prefer not to use that solution as it appears to be a dead end.  There must be something different about how freenx/opennx set up security vs X2Go, but I can't find much documentation on configuring security in X2Go.

I'll spend some more time in the man pages, but any other suggestions here would be greatly appreciated.

Thanks


On Wednesday, December 4, 2013 8:22 PM, Harvey Eneman <harvey.eneman@oracle.com> wrote:
If you haven't already, I suggest that use "ssh -Y" to setup trusted X11
forwarding when you connect to the remote linux box from a terminal
window (eg. xterm) on the "local" linux host.  This will set the DISPLAY
environment variable to a local display on the remote host that is
securely forwarded to local linux host for display on the Windows machine.


On 12/4/13, 5:53 PM, Nick Ingegneri wrote:
> Can anybody assist me with debugging what I am doing wrong in this case?
>
> I am running the X2Go client in Window 7 and the X2Go server on a RedHat 6 machine. I would like to have a remote linux host export the display back to the X2Go server, which would then forward it to the Windows 7 client.
>
> Starting a new X2Go session, this works on the local host:
>
> [user@localmachine ~]$ echo $DISPLAY
> :84
> [user@localmachine ~]$ xhost +
> access control disabled, clients can connect from any host
> [user@localmachine ~]$ xclock
> # note - the xclock starts without problems
>
> But on a remote host, I found I could not connect to that display, even with "xhost +" already set:
>
> [user@remotemachine ~]$ setenv DISPLAY localmachine:84
> [user@remotemachine ~]$ xclock
> Error: Can't open display: localmachine:84
> [user@remotemachine ~]$
>
> As an experiment, I tried setting the DISPLAY on localmachine to use the hostname, after which it could not connect to the display:
>
> user@localmachine ~]$ setenv DISPLAY localmachine:84
> [user@localmachine ~]$ xclock
> Error: Can't open display: localmachine:84
> [user@localmachine ~]$ xhost
> xhost:  unable to open display "localmachine:84"
>
> I'm probably missing something obvious, but don't have any idea what is misconfigured.
>
> Thanks!
>
>
>
> _______________________________________________
> X2Go-User mailing list
> X2Go-User@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/x2go-user

>

_______________________________________________
X2Go-User mailing list
X2Go-User@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-user