<?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 static nat not working in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214958#M357365</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should always use real, not mapped addresses in ACLs when working with post 8.3 code, so do what Colin said.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 30 May 2013 05:13:05 GMT</pubDate>
    <dc:creator>Andrew Phirsov</dc:creator>
    <dc:date>2013-05-30T05:13:05Z</dc:date>
    <item>
      <title>static nat not working</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214956#M357363</link>
      <description>&lt;P&gt;I have a very simple request on 8.6 code, I need to translate a public ip address to a private on a given port, I have the following :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network obj-TEST&lt;/P&gt;&lt;P&gt; host 192.168.10.10&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;object network obj-TEST&lt;/P&gt;&lt;P&gt; nat (inside,outside) static 88.88.88.88&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list incoming_outside extended permit tcp any host 88.88.88.88 eq 3389&lt;/P&gt;&lt;P&gt;access-group incoming_outside in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yet I am not able to RDP to 88.88.88.88 from the outside. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I checked that 192.168.10.10 is reachable from the firewall and the port is open from the inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any idea what's wrong with this config?&lt;/P&gt;&lt;DIV class="mcePaste" id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;"&gt;object network obj-TEST&lt;BR /&gt; nat (inside,outside) static 206.172.40.93&lt;/DIV&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:51:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214956#M357363</guid>
      <dc:creator>network770</dc:creator>
      <dc:date>2019-03-12T01:51:01Z</dc:date>
    </item>
    <item>
      <title>Re:static nat not working</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214957#M357364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try changing the acl from 88.88.88.88 to 192.168.10.10&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2013 02:49:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214957#M357364</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2013-05-30T02:49:03Z</dc:date>
    </item>
    <item>
      <title>static nat not working</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214958#M357365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should always use real, not mapped addresses in ACLs when working with post 8.3 code, so do what Colin said.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2013 05:13:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214958#M357365</guid>
      <dc:creator>Andrew Phirsov</dc:creator>
      <dc:date>2013-05-30T05:13:05Z</dc:date>
    </item>
    <item>
      <title>static nat not working</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214959#M357366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's working now. it looks strange to allow a private ip address incoming to the outside interface, I can't seem to wrap my head around this&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2013 10:55:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214959#M357366</guid>
      <dc:creator>network770</dc:creator>
      <dc:date>2013-05-30T10:55:10Z</dc:date>
    </item>
    <item>
      <title>static nat not working</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214960#M357367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ronni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason for this is the fact that NAT and ACL operations have changed in the new software.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When a connection arrives on the ASA to a NATed destination address the ASA first UNTRANSLATES that public NAT IP address to the local IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So after that phase of processing the packet the destination address is already the local IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the ASA reaches the ACL phase it will therefore need to allow the traffic to the REAL IP address rather than the NAT IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2013 10:57:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214960#M357367</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-30T10:57:24Z</dc:date>
    </item>
    <item>
      <title>static nat not working</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214961#M357368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i need dmz to inside configuration&lt;/P&gt;&lt;P&gt;DMZ Interface IP 10.1.1.1/24&lt;/P&gt;&lt;P&gt;DMZ Server IP 10.1.1.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inside Interface 192.168.11.249&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and regrds&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2013 06:44:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214961#M357368</guid>
      <dc:creator>adittechdha</dc:creator>
      <dc:date>2013-05-31T06:44:17Z</dc:date>
    </item>
    <item>
      <title>static nat not working</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214962#M357369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please start a new discussion for your own questions that arent related to the original topic&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on your software level of your firewall you might not need any NAT configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 May 2013 06:48:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-not-working/m-p/2214962#M357369</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-31T06:48:49Z</dc:date>
    </item>
  </channel>
</rss>

