SEO

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?

Thanks in advance.

Jon

--------------------------------------------
"Opportunity always involves some risk. You can't steal second base
and keep your foot on first."

Jon 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?
>
> Thanks in advance.
>
> Jon

You might want to try giving the sunray server permission to display on
your localhost. From a local shell run

$ /usr/openwin/bin/xhost +sunrayserver

alan.

"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

"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)?

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

I don't think it should and i have not seen the same problem you have in
my use of Sun Rays whilst telnet'd to another machine and running a
piece of X software.

Clutching at straws, are you running a pacthed Sun Ray server? I am
running version 2 patched without problems.

Sorry can't be more help
Ade

"Jon" <jonjhatton@cox.net> wrote:
> "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.
>
> The Sunrays are a thin client system. Meaning that there is no local
> host to grant display privileges to the remote server to.

Your Sun Ray session is completely running on the Sun Ray server,
not on the Sun Ray appliance. The display host is
the Sun Ray server. Just think of a Sun Ray appliance
as a framebuffer.


Thomas

Jon wrote:
> 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)?

This should work - I do it every day.

Sunray is attached to host sunrayserv. Remote server is remoteserv.
remoteserv wants to display to sunrayserv, but on the sunray, not the
server console.


sunrayserv> echo $DISPLAY
:12.0

#My display on the Sun Ray server is 12.0

sunrayserv> xhost +remoteserv

#remoteserv can now display to sunrayserv, but only on display 12.0

sunrayserv> telnet remoteserv
....
....
remoteserv> DISPLAY=sunrayserv:12.0 export DISPLAY
remoteserv> echo $DISPLAY
sunraserv:12.0
remoteserv> xapp &

#The x app should pop up on your sunray on sunrayserv.

You have to do the xhost on your SunRay, not on the server console.
xhost + on display 0.0 is not teh same as xhost + on display 5.0

Unless I'm misunderstanding your question?

Actually the easiest way is to use SSH with X forwarding. Then this all
is automatic & your session is encrypted.

--Mike