"Thomas Dehn" <thomas-usenet@arcor.de> wrote in message news:<c7b7t8$1mb6m$4@ID-57266.news.uni-berlin.de>...
> "Jon" <jonjhatton@cox.net> wrote:
> > I am attempting to telnet to a remote Sun server in order to execute a
> > X application, e.g., xlogo. I set the DISPLAY variable to
> > sunrayserver:session.0 and the remote server is unable to open the
> > display. If I logon directly to the server and set the display to
> > sunrayserver:0.0, then the appliaction runs and the display is sent to
> > the screen.
> >
> > Why can't I get the display to go to my client?
>
> Presumably you failed to authenticate with the Xlib.
> If you login directly at the remote server, then telnet
> to the Sun Ray server, you also have to authenticate
> with the Xlib.
>
> The secure method for Xlib authentication is xauth.
> The preferred somewhat insecure method is
> to type "xhost + <remotehost>" at the display
> system before starting the application on the remote
> system, and remove these access rights when you're done.
>
> In addition, ToolTalk aware applications require
> authentication with ToolTalk.
>
>
> Thomas


The Sunrays are a thin client system. Meaning that there is no local
host to grant display privileges to the remote server to.

When one logs on at a client, they are running on the server with the
display sent to the clients session (sunrayserver:session#.0, e.g.
srvrName:5.0 if I am the 5th session at that time). The session number
changes each time one logs on.

If I log on at the sunrayserver and send the display from the remote
server back to the sunrayserver (srvrName:0.0), everything is fine.
The problems occur when I attempt to send the display to the client
session (srvrName:5.0). I've done the xhost + <remote_server>.

Why should it matter what the session number is, 0 or 5 (or whatever
it is)?