Web Servers on Unix and Linux - Remote display on SGI using NAT behind ADSL router/modem/firewall

This is Interesting: Free IT Magazines  
Home > Archive > Web Servers on Unix and Linux > May 2004 > Remote display on SGI using NAT behind ADSL router/modem/firewall





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Remote display on SGI using NAT behind ADSL router/modem/firewall
Adam Smith

2004-05-20, 2:43 am

I am using an INDGO2, behind an ADSL router and using Network Address
Translation. I tried doing a remote display from another machine but it
did not work, here are the details:

Both machines SGI: Local - INDIGO2 ; Remote - OCTANE both running
6.5.19 O/S

Hypothetical hostnames / IP #
Local LAN side: 192.155.10.9 : WAN side NNN.nnn.xxx.iii

Hostname Remote machine: machine1.target1.com MMM.mmm.jjj.nnn
Router/Gateway 192.155.10.1

SetUp
xhost machine1.target1.com
setenv DISPLAY 192.155.10.9:0

mach1# telnet machine1.target1.com
Trying RRR.sss.ttt.xxx
Connected to machine1.target1.com.
Escape character is '^]'.


IRIX (machine1.target1.com)

Trying machine1.target1.com
login:
...
...
...

programtorun

Error can't open display: 192.155.10.9:0

Does any one have a handle on how to correct this
Thanks

-- Adam --

Tristram Scott

2004-05-20, 5:42 am

Adam Smith wrote:
>
> I am using an INDGO2, behind an ADSL router and using Network Address
> Translation. I tried doing a remote display from another machine but it
> did not work, here are the details:
>
> Both machines SGI: Local - INDIGO2 ; Remote - OCTANE both running
> 6.5.19 O/S
>
> Hypothetical hostnames / IP #
> Local LAN side: 192.155.10.9 : WAN side NNN.nnn.xxx.iii
>
> Hostname Remote machine: machine1.target1.com MMM.mmm.jjj.nnn
> Router/Gateway 192.155.10.1
>
> SetUp
> xhost machine1.target1.com
> setenv DISPLAY 192.155.10.9:0
>
> mach1# telnet machine1.target1.com
> Trying RRR.sss.ttt.xxx
> Connected to machine1.target1.com.
> Escape character is '^]'.
>
> IRIX (machine1.target1.com)
>
> Trying machine1.target1.com
> login:
> ...
> ...
> ...
>
> programtorun
>
> Error can't open display: 192.155.10.9:0
>
> Does any one have a handle on how to correct this
> Thanks
>
> -- Adam --


On the remote machine, setenv DISPLAY NNN.nnn.xxx.iii:0. As far as ther
rest of the world is concerned, your local machine has an IP address of
NNN.nnn.xxx.iii.

If that doesn't work, perhaps try a telnet from the remote machine to
the local one, and see that you can open some sort of communication with
it.

I'm guessing a bit here, but you might also need to tell your router
that incoming X stuff is for the Indogo, and not one of the other local
machines. That might involve reading a few man pages on X and
/etc/services.


--
Dr Tristram J. Scott
Energy Consultant
Neil Rothwell

2004-05-20, 5:42 am

On Thu, 20 May 2004 08:49:16 +0100, Tristram Scott <tristram.scott@ntlworld.com>
wrote:

>Adam Smith wrote:
[vbcol=seagreen]
>
>On the remote machine, setenv DISPLAY NNN.nnn.xxx.iii:0. As far as ther
>rest of the world is concerned, your local machine has an IP address of
>NNN.nnn.xxx.iii.
>
>If that doesn't work, perhaps try a telnet from the remote machine to
>the local one, and see that you can open some sort of communication with
>it.
>
>I'm guessing a bit here, but you might also need to tell your router
>that incoming X stuff is for the Indogo, and not one of the other local
>machines.


Yes, configure your router to re-direct the ports for these incoming request to
192.155.10.9. You need to do that to allow a server behind a simple NAT router
to be seen by the WAN.

Wes Fisher

2004-05-20, 5:43 pm

Using SSH is probably the easiest way. Ditch telnet. Just setup a port
forward on port 22 at your firewall to your IRIX box. Setup SSH tunneling
for X on your ssh client. That's the surefire way for X access remotely.

Praetorius

Thu, 20 May 2004 09:05:06 +0100, Neil Rothwell wrote:

> On Thu, 20 May 2004 08:49:16 +0100, Tristram Scott <tristram.scott@ntlworld.com>
> wrote:
>
>
>
> Yes, configure your router to re-direct the ports for these incoming request to
> 192.155.10.9. You need to do that to allow a server behind a simple NAT router
> to be seen by the WAN.


--
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9">
</HEAD>
<BODY>
Regards,<BR>
<B>G. Wesley Fisher</B><BR>
<I>Information Technician<BR>
G.M Stewart Corp.</I><BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<IMG SRC="file:///usr/share/gtkhtml-3.0/icons/rule-blue-left.png" ALIGN="bottom" BORDER="0">
</TD>
<TD BACKGROUND="file:///usr/share/gtkhtml-3.0/icons/rule-blue-center.png" WIDTH="100%">
<IMG SRC="file:///usr/share/gtkhtml-3.0/icons/transparent.png" ALIGN="bottom" BORDER="0">
</TD>
<TD>
<IMG SRC="file:///usr/share/gtkhtml-3.0/icons/rule-blue-right.png" ALIGN="bottom" BORDER="0">
</TD>
</TR>
</TABLE>
<BR>
<DIV ALIGN=center>P. 307.789.8005 | F. 307.789.5540 | http://www.gmstewart.com</DIV>
</BODY>
</HTML>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com