[FreeNX-kNX] Unable to open Display
Freek de Kruijf
f.de.kruijf at hetnet.nl
Fri Jun 12 07:58:42 UTC 2009
Op vrijdag 12 juni 2009 09:00:07 schreef Daniel Spannbauer:
> Florian Schmidt schrieb:
> > Hi,
> >
> > NX set's locally the Display to 1000 plus the session number (the first
> > one is 0) so the display on your NX server is unix:1000 -> the unix is
> > used for local socket operations only.
> >
> > When you connect to an different machine you need a possibility to
> > connect and forwarding you X11 credentials automatically. Telnet doesn't
> > support X11 forwarding (at least out of the box).
> >
> > So I would suggest that you use ssh -X <hostname> instead to use X11
> > forwarding.
> >
> > If there is any real reason (I can't see any in any case) that you are
> > forced to use telnet (I am wondering that this is still alive :) ) you
> > can set your display than on the machine by setenv DISPLAY
> > <loginserverhostname>:1000 (tcsh) or export
> > DISPLAY=<loginserverhostname>:1000 (bash) and than do an xhost
> > +<hostnamewhereItelnetedto> on your NX LoginServer.
>
> Ok, now I understand the Problem.
> But can I tell NX to use a Display that begins with the Hostname, not
> "unix"?
>
> Regards
>
> Daniel
>
> > Cheers,
> > Florian
Which hostname? unix is in fact the localhost. If you want to go to another
host your NX host is a dispatcher host and you have to look in de
documentation for load balancing, because that's what you are doing with the
NX host.
--
fr.gr.
Freek de Kruijf
More information about the FreeNX-kNX
mailing list