<?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: Access FTP Sever in inside interface with Public IP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482330#M733997</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Correct, if you already have NAT statement on that interface, then you would need the global (inside) command. Otherwise, if there is no NAT statement at all on that interface, you can disable nat-control, and the connection would work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, if you have ACL assigned to the inside interface, you would need to allow the traffic:&lt;/P&gt;&lt;P&gt;access-list &lt;ACL-NAME&gt; permit tcp &lt;INSIDE-SUBNET&gt; &lt;MASK&gt; host &lt;PUBLIC-FTP-IP&gt; eq 21&lt;/PUBLIC-FTP-IP&gt;&lt;/MASK&gt;&lt;/INSIDE-SUBNET&gt;&lt;/ACL-NAME&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 May 2010 10:32:02 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2010-05-04T10:32:02Z</dc:date>
    <item>
      <title>Access FTP Sever in inside interface with Public IP</title>
      <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482325#M733980</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a ftp server in my inside zone of ASA, One of my application team needed to access that ftp server in the inside interface with the Public IP. If they were using a url for that I could have used "dns doctoring". I tried with the following NAT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside, inside) &amp;lt;localip&amp;gt; &amp;lt;publicip&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but ASA thinking that it is an attack &lt;SPAN __jive_emoticon_name="sad" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/sad.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: Both Client and FTP server are in the same network hence the zone which is inside.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:40:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482325#M733980</guid>
      <dc:creator>manuadoor</dc:creator>
      <dc:date>2019-03-11T17:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: Access FTP Sever in inside interface with Public IP</title>
      <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482326#M733982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It should be as follows:&lt;/P&gt;&lt;P&gt;static (inside, inside) &lt;PUBLICIP&gt; &lt;LOCALIP&gt;netmask 255.255.255.255&lt;/LOCALIP&gt;&lt;/PUBLICIP&gt;&lt;/P&gt;&lt;P&gt;global (inside) 1 interface&lt;/P&gt;&lt;P&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 10:05:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482326#M733982</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-05-04T10:05:29Z</dc:date>
    </item>
    <item>
      <title>Re: Access FTP Sever in inside interface with Public IP</title>
      <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482327#M733987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jiveTT-hover-user&amp;nbsp; jive-username-link" href="https://community.cisco.com/people/halijenn" id="jive-16889023,549,844,162,055,370" onmouseout="" onmouseover=""&gt;halijenn&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nat syntax is ilike&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (real int, mapped int) mapped ip&amp;nbsp; real ip netmask &lt;NETMASK&gt; ??/&lt;/NETMASK&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in my case I want to replace my public ip with my local ip, what is the logic behind&amp;nbsp; static (inside, inside) &lt;PUBLICIP&gt; &lt;LOCALIP&gt;netmask&amp;nbsp; 255.255.255.255&lt;/LOCALIP&gt;&lt;/PUBLICIP&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Also pls let me know why we require the following??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (inside) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is just to clear my understanding!!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 10:14:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482327#M733987</guid>
      <dc:creator>manuadoor</dc:creator>
      <dc:date>2010-05-04T10:14:08Z</dc:date>
    </item>
    <item>
      <title>Re: Access FTP Sever in inside interface with Public IP</title>
      <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482328#M733990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For normal static (inside,outside) statement, you would configure the following: static (inside,outside) &lt;PUBLIC-IP&gt; &lt;LOCAL-IP&gt;, so the concept is the same for static (inside,inside).&lt;/LOCAL-IP&gt;&lt;/PUBLIC-IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are trying to reach the public ip, so the first ip address in the static statement should be the public-ip, and the second ip is the local-ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason why you need "global (inside) 1 interface" is you still need translation for the source address which is your internal host. The static statement above is for destination translation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 10:21:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482328#M733990</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-05-04T10:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: Access FTP Sever in inside interface with Public IP</title>
      <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482329#M733994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class="jive-rendered-content"&gt;The first part is clear now ,, &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV class="jive-rendered-content"&gt;Since the host and the server is in the same zone (inside), why we need source translaion??? You meant for nat-control??&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 10:28:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482329#M733994</guid>
      <dc:creator>manuadoor</dc:creator>
      <dc:date>2010-05-04T10:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: Access FTP Sever in inside interface with Public IP</title>
      <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482330#M733997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Correct, if you already have NAT statement on that interface, then you would need the global (inside) command. Otherwise, if there is no NAT statement at all on that interface, you can disable nat-control, and the connection would work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, if you have ACL assigned to the inside interface, you would need to allow the traffic:&lt;/P&gt;&lt;P&gt;access-list &lt;ACL-NAME&gt; permit tcp &lt;INSIDE-SUBNET&gt; &lt;MASK&gt; host &lt;PUBLIC-FTP-IP&gt; eq 21&lt;/PUBLIC-FTP-IP&gt;&lt;/MASK&gt;&lt;/INSIDE-SUBNET&gt;&lt;/ACL-NAME&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 10:32:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482330#M733997</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-05-04T10:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: Access FTP Sever in inside interface with Public IP</title>
      <link>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482331#M734000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a lot.. Let me try now!!!&lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 May 2010 10:33:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-ftp-sever-in-inside-interface-with-public-ip/m-p/1482331#M734000</guid>
      <dc:creator>manuadoor</dc:creator>
      <dc:date>2010-05-04T10:33:15Z</dc:date>
    </item>
  </channel>
</rss>

