Hi Terry,
> > http://www.straightrunning.com/XmingNotes/ is one Windows X server,
> > and I tend to use xclock(1) as a simple test X client. You may want
> > to make sure it will display OK when sitting at the SparcStation's
> > screen before using it to test connecting to a remote X server.Â
>
> X is running on the SparcStation and is used for a number of things,
> including the dialog boxes used for our scripts.
I don't doubt it, but I'm trying to establish that xclock(1) works when
sitting at the Sparc so we can use it as a test X client when trying to
make it display on the PC. :-) So you need to sit at the Sparc, log in
to an X environment and type "xclock" in a terminal window. Does a
clock appear? Closing the window should give you the next shell prompt.
> > > 6. In your telnet session type, DISPLAY=windows_hostname_or_ip_address:0.0
> > > 7. In your telnet session type, export DISPLAY
> > > ...
> > > I'm OK until I get to step 6, when I get a 'Command not
> > > recognised' error. Is sending that command via the telnet session
> > > causing the problem or am I missing something else?
> >
> > You probably have a C shell on the Sun. Replace 6 and 7 with
> >
> >Â Â Â setenv DISPLAY windows_hostname_or_ip_address:0.0
>
> Excellent! A step forward. Unfortunately, there doesn't seem to be
> an export command in the csh.
There isn't. But the "export DISPLAY" is step 7 and I said "6 and 7".
:-)
> According to the man page it is available in sh and ksh, but not csh.Â
> Any idea how I do the last step?
To set an environment variable in sh is
FOO=bar
export FOO
and in csh it's
setenv FOO bar
so no extra step is required.
> Thanks. I've now got that far, but still no graphical display at the
> PC end when I run my script. I don't suppose that there is any reason
> why the SparcServer wouldn't do this? Could it have been set up
> originally to prevent remote graphical working? In use, this device
> is normally part of an ATE system and has a monitor permanently
> connected so remote logins wouldn't normally be needed.
Please stop using your in-house script. I know it's what you want to
get working but we can't trust its diagnostics when something doesn't go
to plan. That's why xclock, a simple X client, is useful.
So try stages 1-5 as Cygwin suggested before, then the setenv instead of
6 and 7, and then "xclock" having already tried it sitting at the Sparc
as described above. If it appears on the PC, perhaps within the X
server's "root" window rather than in its own window then you can run X
clients on the Sparc and display them on the PC. You test script should
work too.
If not, what happens exactly? There may be a one line error, e.g.
connection refused. The output of
telnet 192.168.1.42 6000
on the Sparc, substituting the PC's real IP address, may also be useful.
That's trying to connect to the TCP port 6000 which is the port an X
server for display 0 will listen on. When you set DISPLAY to ...:0
you're specifying display 0. :1 would be display 1, TCP port 6001, and
so on. If telnet says it's connected then you can't do anything useful
other than kill it but it does show that something's is listening on
that port on the PC and you can get to it.
It could be the Cygwin X server that you've gone with doesn't listen for
connections from X clients on network interfaces by default, perhaps for
security, but I doubt it given their instructions you quoted.
Is it possible that your corporate LAN configuration is blocking TCP
port traffic around 6000?
Cheers,
Ralph.
--
Next meeting: Crown Hotel, Blandford Forum, Tuesday 2010-11-02 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
How to Report Bugs Effectively: http://goo.gl/4Xue
