<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ASA - Policy NAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-policy-nat/m-p/1542858#M611451</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, you cannot do policy NAT for multiple inside IP and one public IP. You do need to find a way to differentiate the traffic on the outside interface. You can use different ports for different servers. But you cannot have both devices advertise their services using the same public IP and same port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Sep 2010 20:47:34 GMT</pubDate>
    <dc:creator>Nagaraja Thanthry</dc:creator>
    <dc:date>2010-09-15T20:47:34Z</dc:date>
    <item>
      <title>ASA - Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/asa-policy-nat/m-p/1542857#M611448</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to find out if possible to do the following:&lt;/P&gt;&lt;P&gt;I have a server in the DMZ: 172.17.1.100 /24 and server in the inside 172.20.1.200 /24 both will have the same nat ip&lt;/P&gt;&lt;P&gt;address outside: 1.1.1.200 this can be done using policy nat. ( I think, have not done yet).&lt;/P&gt;&lt;P&gt;Let say the above policy nat is implemented and the real questions here are: &lt;/P&gt;&lt;P&gt;1. if outside users connect to 1.1.1.200 then which servers the outside users will connect.&lt;/P&gt;&lt;P&gt;2. If posible for the outside user connect to 1.1.1.200 and this will redirect to DMZ server 172.17.1.100 instead of inside server 172.20.1.200&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is still in planning mode so no actual configuration has been done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:40:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-policy-nat/m-p/1542857#M611448</guid>
      <dc:creator>ttran</dc:creator>
      <dc:date>2019-03-11T18:40:57Z</dc:date>
    </item>
    <item>
      <title>Re: ASA - Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/asa-policy-nat/m-p/1542858#M611451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, you cannot do policy NAT for multiple inside IP and one public IP. You do need to find a way to differentiate the traffic on the outside interface. You can use different ports for different servers. But you cannot have both devices advertise their services using the same public IP and same port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Sep 2010 20:47:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-policy-nat/m-p/1542858#M611451</guid>
      <dc:creator>Nagaraja Thanthry</dc:creator>
      <dc:date>2010-09-15T20:47:34Z</dc:date>
    </item>
    <item>
      <title>Re: ASA - Policy NAT</title>
      <link>https://community.cisco.com/t5/network-security/asa-policy-nat/m-p/1542859#M611456</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your response NT.&amp;nbsp; I will work on different solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Sep 2010 21:04:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-policy-nat/m-p/1542859#M611456</guid>
      <dc:creator>ttran</dc:creator>
      <dc:date>2010-09-15T21:04:02Z</dc:date>
    </item>
  </channel>
</rss>

