Run SAM remotely via telnet

[Robert Funk_1]

Hi, I'm a newbie at HP-UX and am attempting to run SAM remotely from my Win2K PC via telnet.
# /usr/bin/X11/xhost +
/usr/bin/X11/xhost: unable to open display "x.x.x.x:0.0"
# export DISPLAY=x.x.x.x:0.0
(where x's are my ip address)
# /usr/sbin/sam&
[1] 15328
#
The DISPLAY environment variable is set to "x.x.x.x:0.0", but
the current configuration won't allow sam to run on that display.

The DISPLAY environment variable may be incorrect, or, if you are
running sam remotely, you may need to allow the remote system
to access your local X server by typing

/usr/bin/X11/xhost +hostname

on your local machine.

Do you want to proceed using the terminal version of sam?
(yes or no) [yes]

Can anybody steer me in the right direction? Thanks, Robert

[Patrick Wallek]

If you are running sam from a basic telnet session then you won't be able to run the GUI version of sam.

Once you get logged into the machine, just type:

#/usr/sbin/sam

And run the terminal version of SAM. If you have your TERM set correctly, it should run just fine.

[Jeff Schussele]

Hi Robert,

You must have some kind of X window running to except an X-session.
If you're on an HP workstation that's running X already, then all you need to do is run
xhost +
to accept any X-session.

If you're on a Windoze system then you'll need to run something like Exceed or Chameleon to accept X-sessions.

Rgds,
Jeff

[Kurt Beyers.]

A simple telnet session won't allow a graphic session. You need to run an X-server (Reflection, Exceed Hummingburd, ...) on your on your Win2k box to have a graphical session of SAM.

Via an ordinary telnet session, you can run the terminal version of SAM without any problems. Don't export the DISPLAY variable and launch SAM directly. I'm always use the terminal session of SAM, it has the same features as the graphical version.

Kurt

[S.K. Chan]

Here we use ReflectionX to display any X window application (including SAM) running on an HP workstation onto the PC. A regular telnet from w2k will not work. Running the ascii/terminal version of SAM works equally well.

[Patrick Wallek]

Maybe I'm confused about your problem.

But if you just login to the machine, and DON'T do an xhost, and DON'T export your DISPLAY the running 'sam' will start the terminal version of SAM. You have all the same functionality of the GUI version.

[Robert Funk_1]

Thanks to all who posted replies - I can't believe how responsive you all are!

I failed to mention that I do have Exceed loaded on a Win2K PC, but thanks to your answers, figured out I needed to have it up and running in the background prior to running the export command and kicking off SAM.

I am now successfully able to access SAM remotely!

Thanks again,
Robert