<div>
You won't be able to given the conditions you've described - remember that the NAT/PAT is applied at the firewall and since both devices are on the same network segment, the inside traffic will never reach it - it'll go direct on the inside segment.<br />

</div>


You won't be able to given the conditions you've described - remember that the NAT/PAT is applied at the firewall and since both devices are on the same network segment, the inside traffic will never reach it - it'll go direct on the inside segment.


<div>
<div class="content wysiwyg-content">
I am familiar with the NAT and PAT outside-to-DMZ. &nbsp;E.g. map public IP 1.2.3.4 on the outside interface to private address 192.168.100.4 on the DMZ. &nbsp;<br />
<br />
But now consider the case where there is an inside interface on the ASA with address 192.168.200.1. And there is a host on the inside network &quot;insider-1&quot; with address 192.168.200.50. &nbsp;insider-1 resolves outsider-1 as 1.2.3.4. &nbsp;How can I configure the ASA so that insider-1 is able to speak to outsider-1 using address 1.2.3.4?<br />
<a href="https://filedb.experts-exchange.com/incoming/2009/12_w01/217910/ScreenHunter-01-Dec.-30-09.13.gif" target="_blank" class="file-inline" title="Diagram - insider-1 to talk to outsider-1 using latter's public IP (19 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>ScreenHunter-01-Dec.-30-09.13.gif</a>
</div>
</div>


Diagram - insider-1 to talk to outsider-1 using latter's public IP

ScreenHunter-01-Dec.-30-09.13.gif

I am familiar with the NAT and PAT outside-to-DMZ.  E.g. map public IP 1.2.3.4 on the outside interface to private address 192.168.100.4 on the DMZ.  

But now consider the case where there is an inside interface on the ASA with address 192.168.200.1. And there is a host on the inside network "insider-1" with address 192.168.200.50.  insider-1 resolves outsider-1 as 1.2.3.4.  How can I configure the ASA so that insider-1 is able to speak to outsider-1 using address 1.2.3.4?

NAT/Alias question - Cisco ASA 5510

Cisco PIX is a dedicated hardware firewall appliance; the Cisco Adaptive Security Appliance (ASA) is a firewall and anti-malware security appliance that provides unified threat management and protection the PIX does not. Other Cisco devices and systems include routers, switches, storage networking, wireless and the software and hardware for PIX Firewall Manager (PFM), PIX Device Manager (PDM) and Adaptive Security Device Manager (ASDM).

Cisco

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.