Maybe a picture below helps explain it better.
----------------
+ 63.98.3.64 +
+ outside FW +
----------------
|
--+ ISP firewall +--
|
------------------------
+ 172.16.5.47 +
+ ISP IP - my system +
+ my firewall (FW) +
+ (Linux box) +
+ 192.168.1.1 +
+ int. IP - my server +
------------------------
|
-------------------------- --------------------------
+ 192.168.1.19 +----------+ 192.168.1.2 +
+ Linux - apache, etc. + + MS machine +
-------------------------- + sees all int. machines +
--------------------------
I should have sent this initially - sorry about that. The MS machine(s) are
all connected via hub to the server, etc. I just did not mess with putting
a line from MS to my server.
I have put the 63.98.3.64 into my Hosts and Lmhosts files on the windows
machine. I have put it in two ways ... one with a name (I can ping "name"
and it tries to find 63.98.3.64) ... plus one with IP addy of the internal
machine 192.168.1.19 ... to no avail ... which probably means I do not know
what I am doing and set it up wrong.
I do not have DNS running on my server - do not want to hassle with it, etc.
I just use the ISPs DNS.
Does this shed more light on the subject?
-----Original Message-----
From: Sam MacDonald [mailto:smac at visi.com]
Sent: Tuesday, May 17, 2005 9:40 PM
To: Randy Clarksean
Cc: tclug
Subject: Re: [tclug-list] OT: local redirect of IP addy
Just so I know I'm looking at this right.
the internal machine is addressed as 63.98.3.64
you can get to it using the above address
the external address assigned by your ISP 172.16.5.47
you can NOT get to it using this address
I can't ping this address and the address times out using Firefox
trace route dies at c6400-nrp-3.border.mpls.visi.com
So this address is not associated with a web resource in DNS that
I can tell.
Is the internal DNS setup properly for this specific machine?
do you have an internal DNS server running?
Is http.config setup properly?
Are you accessing the Linux machine with an M$ machine?
if so FQDN (fully qualified domain name)
Can you get to the machine using the FQDN? what ever it is?
If this is an M$ machine you are attempting to access the web server from
Put the name and IP address in the Host fine in
c:\"systemroot"\system32\drivers\etc (XP or 2K)
systemroot is the windows directory
Sam.
Randy Clarksean wrote:
>I have mediaWiki installed on a Linux box behind my firewall with a local
IP
>address. I have to view these pages by using the internal IP addy.
>
>Issue: I would like to be able to use the real world IP address all the
>time to view the pages, rather than the internal IP address. For some
>reason when I use the IP address 63.98.3.64 on a machine internal to the
>network ... the connection times out and it does not find anything.
>
>But, if I use the internal IP address it works just fine ... finds the
>machine I am redirecting a port to, etc.
>
>To further complicate it, the IP address I am assigned by my ISP is
>172.16.5.47 ... an internal IP addy (high speed wireless connection). They
>redirect all traffic to my real world IP addy and open all ports up to my
>server. All works well, except for this one issue where I can not use the
>63.98.3.64 IP addy to get to anything. It would be nice to use that addy,
>or redirect to it with a name to simplify how pages are looked up, etc.
>
>Any thoughts or suggestions as to what I might have set up wrong, or what
my
>ISP might need to do to allow me to see that IP addy? I can not even ping
>the addy and get a response.
>
>Thanks in advance for any input.
>
>Randy
>
>
>
>_______________________________________________
>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
>tclug-list at mn-linux.org
>http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>
>
>