Re: destination NAT

From: Manouchehr Omari <manouchehr1979_at_gmail.com>
Date: Mon, 5 Dec 2011 04:07:07 -0600

You just have to replace DMZ with inside, if you have done the rest of the
configuration correctly it should work.

static (inside,outside) tcp PUBLIC_IP www WEB_SERVER_IP www netmask
255.255.255.255

On Mon, Dec 5, 2011 at 3:49 AM, amin <amin_at_axizo.com> wrote:

> It is in the inside.****
>
> ** **
>
> *From:* Manouchehr Omari [mailto:manouchehr1979_at_gmail.com]
> *Sent:* Monday, December 05, 2011 11:43 AM
> *To:* amin
> *Cc:* ccielab_at_groupstudy.com
> *Subject:* Re: destination NAT****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> If your servers are in DMZ your configuration would be something like this,
> ****
>
> ** **
>
> static (DMZ,outside) tcp PUBLIC_IP www WEB_SERVER_IP www netmask
> 255.255.255.255****
>
> ** **
>
> ** **
>
> ** **
>
> On Mon, Dec 5, 2011 at 1:59 AM, amin <amin_at_axizo.com> wrote:****
>
> Hi experts,
>
>
>
> About destination NAT as a solution for accessing the published server IP
> address from inside network, what would be the configuration if the server
> inside and I want them to access it using its public address
>
>
>
> This is the configuration if it is on the DMZ,
>
>
>
> static (dmz,outside) 172.20.1.10 10.10.10.10 netmask 255.255.255.255
>
>
>
> static (dmz,inside) 172.20.1.10 10.10.10.10 netmask 255.255.255.255
>
>
>
>
>
> Regards,
>
> Amin
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
> ****
>
> ** **

Blogs and organic groups at http://www.ccie.net
Received on Mon Dec 05 2011 - 04:07:07 ART

This archive was generated by hypermail 2.2.0 : Sun Jan 01 2012 - 08:27:00 ART