<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffcc" text="#000000">
In a number of cases NATs have a problem to access the internal
boxes via an external address from inside the NAT.<br>
<br>
In such cases it is much easier to just access the box from inside
with it's internal address and from outside with its external
address.<br>
<br>
Using the two views allows for all sorts of scripting etc. without
having to consider whether you are on the outside or the inside. I
have used that for many years now.<br>
<br>
On 30/05/11 21:20, Doug Barton wrote:
<blockquote cite="mid:4DE3EDEB.20606@dougbarton.us" type="cite">On
05/29/2011 23:17, babu dheen wrote:
<br>
<blockquote type="cite">We have DNS record called
"mail.company.com" which is hosted in internal
<br>
company LAN network. When any users try to access
mail.company.com in
<br>
browser, they will get private IP address and immediately they
will get
<br>
mail.company.com website home page whereas if any of my company
users
<br>
try to access the mail.company.com website from internet(outside
<br>
company), they should get public IP address which should be
pointed to
<br>
mail.company.com website.
<br>
</blockquote>
<br>
It's not clear to me from this description why you need 2
different IP addresses for the same resource.
<br>
<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>