<?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: PIX - static NAT troubles in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423476#M536008</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Comoms,&lt;/P&gt;&lt;P&gt;  This is your problem:&lt;/P&gt;&lt;P&gt;1) Here you say do not NAT this traffic.&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list inside_outbound_nat0_acl&lt;/P&gt;&lt;P&gt;access-list inside_outbound_nat0_acl permit ip any xxx.242.139.160 255.255.255.224&lt;/P&gt;&lt;P&gt;2)Then you use this for static nat.&lt;/P&gt;&lt;P&gt;static (inside,outside) xxx.242.139.164 192.168.1.13 dns netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;3)This is totally wrong,first u say do not NAT this traffic then you try to NAT it.How will it work?&lt;/P&gt;&lt;P&gt;4)Even if uou allow with ACL it will not work.&lt;/P&gt;&lt;P&gt;5)Please check your NAT,STATIC NAT,ACL n Routes again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;MAR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Jul 2005 08:02:31 GMT</pubDate>
    <dc:creator>mrarahman</dc:creator>
    <dc:date>2005-07-01T08:02:31Z</dc:date>
    <item>
      <title>PIX - static NAT troubles</title>
      <link>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423473#M536004</link>
      <description>&lt;P&gt;I am trying to make a static route from xxx.242.139.164 to 192.168.1.13 and open ports 25 and 443. I am at a loss for what I missed to make this happen. I would also like to have ICMP traffic open or at least echo-reply so I can test the IPs and that doesn't seem to work either. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX config attached as .txt file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any help!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:14:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423473#M536004</guid>
      <dc:creator>comoms_dot_com</dc:creator>
      <dc:date>2020-02-21T08:14:47Z</dc:date>
    </item>
    <item>
      <title>Re: PIX - static NAT troubles</title>
      <link>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423474#M536006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;my first glance looks like your static statemnet has DNS in the line---&amp;gt; "static (inside,outside) xxx.242.139.164 192.168.1.13 dns netmask 255.255.255.255 0 0" you might want to remove "dns".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next, looks like you do not have an access-list setup that is assigned to the outside interface. To do this you need to define the access list and then use the "access-group" command to assign to the outside interface. You do have some access-list statements in the config but are assigned to "100". You need to create and access-list for Internet traffic coming into inside network. My below acl example uses "outside_inbound" as the acl name, this can be whatever you want, but this follows the same logic as your other acl's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So here is what I think needs to happen:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) xxx.242.139.164 192.168.1.13 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_inbound permit tcp any host xxx.242.139.164 eq https&lt;/P&gt;&lt;P&gt;access-list outside_inbound tcp any host xxx.242.139.164 eq smtp&lt;/P&gt;&lt;P&gt;access-list outside_inbound permit icmp any host xxx.242.139.164 echo-reply&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group outside_inbound in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jul 2005 03:30:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423474#M536006</guid>
      <dc:creator>mkirbyii</dc:creator>
      <dc:date>2005-07-01T03:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: PIX - static NAT troubles</title>
      <link>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423475#M536007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have completed the commands and am still not having luck sending pings to the IP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have attached my current config at pix_config_1.txt for review.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you again, I truly appreciate the help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jul 2005 06:07:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423475#M536007</guid>
      <dc:creator>comoms_dot_com</dc:creator>
      <dc:date>2005-07-01T06:07:54Z</dc:date>
    </item>
    <item>
      <title>Re: PIX - static NAT troubles</title>
      <link>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423476#M536008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Comoms,&lt;/P&gt;&lt;P&gt;  This is your problem:&lt;/P&gt;&lt;P&gt;1) Here you say do not NAT this traffic.&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list inside_outbound_nat0_acl&lt;/P&gt;&lt;P&gt;access-list inside_outbound_nat0_acl permit ip any xxx.242.139.160 255.255.255.224&lt;/P&gt;&lt;P&gt;2)Then you use this for static nat.&lt;/P&gt;&lt;P&gt;static (inside,outside) xxx.242.139.164 192.168.1.13 dns netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;3)This is totally wrong,first u say do not NAT this traffic then you try to NAT it.How will it work?&lt;/P&gt;&lt;P&gt;4)Even if uou allow with ACL it will not work.&lt;/P&gt;&lt;P&gt;5)Please check your NAT,STATIC NAT,ACL n Routes again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;MAR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jul 2005 08:02:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423476#M536008</guid>
      <dc:creator>mrarahman</dc:creator>
      <dc:date>2005-07-01T08:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: PIX - static NAT troubles</title>
      <link>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423477#M536009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The inside host machine will respond to the ping, not the PIX. So make sure the inside host has no firewall enabled that will drop ICMP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ping is a useful tool and often used to troubleshoot internet connectivity etc. I would suggest adding this line to your outside ACL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;acess-l outside permit icmp any any echo-reply&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow pings from the inside network to go to the net and come back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are trying to ping the IP you are mapping to the inside host from the net your ACL does not permit this. You would need the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-l outside permit icmp any host x.x.x.x echo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are the other services that are permitted in the ACL working?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jul 2005 16:42:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-static-nat-troubles/m-p/423477#M536009</guid>
      <dc:creator>dbellaze</dc:creator>
      <dc:date>2005-07-01T16:42:42Z</dc:date>
    </item>
  </channel>
</rss>

