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