<?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: Outside NAT Problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198893#M877689</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vlad &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okay, let me know what happens. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"but if this would be succesful then where is the point of having this feature if it does not work with the rest of the interfaces as well?"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can't answer that unfortunately - leave that one to Cisco i think &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Jan 2009 19:33:11 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2009-01-14T19:33:11Z</dc:date>
    <item>
      <title>Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198883#M877666</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a PIX 515 6.3 and I want to have the LAN behind a DMZ to access the servers on the inside LAN and also the remote hosts which are routed on a L3 switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I did :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (DMZ) 4 192.168.4.0 255.255.255.0 outside 0 0&lt;/P&gt;&lt;P&gt;global (inside) 4 172.16.10.10&lt;/P&gt;&lt;P&gt;access-list DMZ-TEST permit ip 192.168.4.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And it does not work. &lt;/P&gt;&lt;P&gt;I get back " No transaltion group found".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the PIX:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco PIX Firewall Version 6.3(4)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 DMZ security20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help!&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:37:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198883#M877666</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2019-03-11T14:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198884#M877667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vlad,&lt;/P&gt;&lt;P&gt;On the pix due to security levels, it is mandatory to have a static translation when coming from a lower security interface (dmz 20) to a higher security interface (inside 100) you need to define a static like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) X.X.X.X Y.Y.Y.Y where X.X.X.X is the address that you are natting your internal server/network and Y.Y.Y.Y is the real ip for that server/network&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 17:13:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198884#M877667</guid>
      <dc:creator>Ivan Martinon</dc:creator>
      <dc:date>2009-01-14T17:13:52Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198885#M877671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ivan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;" it is mandatory to have a static translation when coming from a lower security interface (dmz 20) to a higher security interface (inside 100)"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure it is. I have configured the following many times &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (outside) 1 192.168.5.0 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;global (inside) 1 172.10.1.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where all source addresses of 192.168.5.x coming in from the outside will be translated to 172.10.1.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this not a supported configuration ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 17:17:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198885#M877671</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2009-01-14T17:17:33Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198886#M877676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ivan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought the same, then I did the static translation and it still didnt work.&lt;/P&gt;&lt;P&gt;And anyway , if I have 100 servers and 30 networks to access I have to do all those statics.&lt;/P&gt;&lt;P&gt;Sounds a bit absurd.&lt;/P&gt;&lt;P&gt;I was checking some documents on cisco, and there was mentioned that this configuration should work.&lt;/P&gt;&lt;P&gt;It definately works with ASA.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 17:59:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198886#M877676</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2009-01-14T17:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198887#M877679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyway ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the keyword outside at the end allows the traffic from lower sec to higher security.&lt;/P&gt;&lt;P&gt;My problem is that I get" No transaltion group found "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 18:02:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198887#M877679</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2009-01-14T18:02:20Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198888#M877681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only difference between your config and the one i have used many times before is the fact that your lower security interface is the DMZ interface and not the outside interface but looking at the command reference for 6.3 it only talks about lower to higher and having to use the "outside" keyword ie. it doesn't say it has to be specifically the outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately i don't have a pix to test with so am of limited help but as previously discussed i know this works outside -&amp;gt; inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 18:05:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198888#M877681</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2009-01-14T18:05:15Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198889#M877683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It definetly works with 7.0, but it says it was introduced with 6.2 so it should work with mine as well.&lt;/P&gt;&lt;P&gt;I dont really understand why ...? Could it be a bug in the IOS ...is there anybody aware of this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A bit of help here people,c'mon!&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 18:10:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198889#M877683</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2009-01-14T18:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198890#M877685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does the interface name have to be outside...I mean I dont think so, sounds a bit ...&lt;/P&gt;&lt;P&gt;I suppose it reffers to traffic from lower to higher ...not specifically outside---&amp;gt; inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 18:15:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198890#M877685</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2009-01-14T18:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198891#M877687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Does the interface name have to be outside" - well that's what i have done before but as i say the command reference for 6.3 suggests it just has to be a lower security interface. Could you run a quick test with outside or is this not possible ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can guarantee it works on 6.x because that was the version of code i used this configuration on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 18:40:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198891#M877687</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2009-01-14T18:40:10Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198892#M877688</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a test fw , so yes I will try with the outside interface tomorrow and let you know the result ,but if this would be succesful then where is the point of having this feature if it does not work with the rest of the interfaces as well?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 19:26:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198892#M877688</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2009-01-14T19:26:44Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198893#M877689</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vlad &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okay, let me know what happens. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"but if this would be succesful then where is the point of having this feature if it does not work with the rest of the interfaces as well?"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can't answer that unfortunately - leave that one to Cisco i think &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 19:33:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198893#M877689</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2009-01-14T19:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198894#M877690</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just did this and guess what : " NO translation group found".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the config :&lt;/P&gt;&lt;P&gt;ccess-list acl-in permit ip any any&lt;/P&gt;&lt;P&gt;access-list acl-in permit icmp any any&lt;/P&gt;&lt;P&gt;access-list out permit ip any any&lt;/P&gt;&lt;P&gt;access-list out permit icmp any any&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;logging on&lt;/P&gt;&lt;P&gt;logging standby&lt;/P&gt;&lt;P&gt;logging monitor informational&lt;/P&gt;&lt;P&gt;logging buffered informational&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;ip address outside 192.168.4.1 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address inside 10.10.10.1 255.255.255.0&lt;/P&gt;&lt;P&gt;ip audit info action alarm&lt;/P&gt;&lt;P&gt;ip audit attack action alarm&lt;/P&gt;&lt;P&gt;pdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;global (inside) 1 interface&lt;/P&gt;&lt;P&gt;nat (outside) 1 192.168.4.0 255.255.255.0 outside 0 0&lt;/P&gt;&lt;P&gt;access-group out in interface outside&lt;/P&gt;&lt;P&gt;access-group acl-in in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Jan 2009 09:50:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198894#M877690</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2009-01-15T09:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198895#M877691</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have a hammer you could use on the pix ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just found this bug - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSCee85940 Bug Details  Bug #18 of 289 | &amp;lt; Previous | Next &amp;gt;  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; outside nat not working  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Symptom: "outside nat" configured using nat and global statements is not working.&lt;/P&gt;&lt;P&gt;Conditions: When traffic is initiated from low security interface side, source nating or bidirectional nating&lt;/P&gt;&lt;P&gt;Workaround: Use static nat for source nat or bidirectional nat  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now it says it's fixed in 6.3(4) but at the same time it says it is first found in 6.3(4). Any chance you could ugrade to 6.3(5) and retest ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Jan 2009 11:57:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198895#M877691</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2009-01-15T11:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198896#M877692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought about a bug also and the confiuration pasted here is from a 6.3(5) and it does not work.&lt;/P&gt;&lt;P&gt;So , I think the hammer is the ultimate solution in solving this. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Jan 2009 12:17:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198896#M877692</guid>
      <dc:creator>hunnetvl01</dc:creator>
      <dc:date>2009-01-15T12:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Outside NAT Problem</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198897#M877693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;TNT would be more fun. I don't see why ANYONE would buy an ASA. What a POS. Object tracking blows, Nat0 BS blows. No route map capability and it is F*ing SLOOOOOW. Get a router - you cant lose!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Apr 2009 07:00:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat-problem/m-p/1198897#M877693</guid>
      <dc:creator>Gerard Roy</dc:creator>
      <dc:date>2009-04-03T07:00:46Z</dc:date>
    </item>
  </channel>
</rss>

