<?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: NAT issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125280#M893907</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;Sorry I was a little to vague.&lt;/P&gt;&lt;P&gt;Here is an example of the config that I currently have in place that does not work correctly:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.3.0 255.255.255.0 host 172.16.199.207 eq smtp &lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.209.64 255.255.255.192 host 172.16.199.207 eq smtp &lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.3.0 255.255.255.0 host 172.16.199.208 eq smtp &lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.209.64 255.255.255.192 host 172.16.199.208 eq smtp &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group inbound2 in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 2 interface &lt;/P&gt;&lt;P&gt;global (outside) 1 172.16.199.202&lt;/P&gt;&lt;P&gt;global (outside) 3 172.16.199.206&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;nat (inside) 2 access-list allownat&lt;/P&gt;&lt;P&gt;nat (inside) 1 10.99.99.33 255.255.255.255&lt;/P&gt;&lt;P&gt;nat (inside) 3 10.99.99.61 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 172.16.199.207 smtp 10.99.99.61 smtp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 172.16.199.208 smtp 10.99.99.33 smtp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The IP of the "interface" is 172.16.199.194&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whenever I check to see what IP I am showing to the world as on the 10.99.99.61 server it always comes back to 172.16.199.194 but I want it to be 172.16.199.206.&lt;/P&gt;&lt;P&gt;But I do not want to change what the rest of the clients going out to the world are seen as which should stay 172.16.199.194.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Nov 2008 21:31:28 GMT</pubDate>
    <dc:creator>joeduea67</dc:creator>
    <dc:date>2008-11-06T21:31:28Z</dc:date>
    <item>
      <title>NAT issue</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125278#M893902</link>
      <description>&lt;P&gt;I am having problems getting a server on the inside of my network to be seen as a specific IP to the world.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The inside server is 10.99.99.61&lt;/P&gt;&lt;P&gt;The outside address should be 172.16.199.206&lt;/P&gt;&lt;P&gt;The global address for the PIX is 172.16.199.194&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What statements should I have in place to make it map correctly?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:09:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125278#M893902</guid>
      <dc:creator>joeduea67</dc:creator>
      <dc:date>2019-03-11T14:09:24Z</dc:date>
    </item>
    <item>
      <title>Re: NAT issue</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125279#M893905</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 172.16.199.206 10.99.99.61&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then you will need to add into your acl on the outside interface &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_in permit tcp any host 172.16.199.206 eq www&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note - i have given an example using http. you can modify to match what you want to allow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit - if you don't already have an acl on the outside interface you will need to apply the acl from above &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group outside_in in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Be aware that there is an implicit "deny ip any any" at the end of any access-list.&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, 06 Nov 2008 20:29:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125279#M893905</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-11-06T20:29:03Z</dc:date>
    </item>
    <item>
      <title>Re: NAT issue</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125280#M893907</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;Sorry I was a little to vague.&lt;/P&gt;&lt;P&gt;Here is an example of the config that I currently have in place that does not work correctly:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.3.0 255.255.255.0 host 172.16.199.207 eq smtp &lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.209.64 255.255.255.192 host 172.16.199.207 eq smtp &lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.3.0 255.255.255.0 host 172.16.199.208 eq smtp &lt;/P&gt;&lt;P&gt;access-list inbound2 extended permit tcp 192.168.209.64 255.255.255.192 host 172.16.199.208 eq smtp &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group inbound2 in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 2 interface &lt;/P&gt;&lt;P&gt;global (outside) 1 172.16.199.202&lt;/P&gt;&lt;P&gt;global (outside) 3 172.16.199.206&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;nat (inside) 2 access-list allownat&lt;/P&gt;&lt;P&gt;nat (inside) 1 10.99.99.33 255.255.255.255&lt;/P&gt;&lt;P&gt;nat (inside) 3 10.99.99.61 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 172.16.199.207 smtp 10.99.99.61 smtp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 172.16.199.208 smtp 10.99.99.33 smtp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The IP of the "interface" is 172.16.199.194&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whenever I check to see what IP I am showing to the world as on the 10.99.99.61 server it always comes back to 172.16.199.194 but I want it to be 172.16.199.206.&lt;/P&gt;&lt;P&gt;But I do not want to change what the rest of the clients going out to the world are seen as which should stay 172.16.199.194.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Nov 2008 21:31:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125280#M893907</guid>
      <dc:creator>joeduea67</dc:creator>
      <dc:date>2008-11-06T21:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: NAT issue</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125281#M893908</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you remove &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 3 10.99.99.61 255.255.255.255&lt;/P&gt;&lt;P&gt;global (outside) 3 172.16.199.206 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and in it's place put &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 172.16.199.206 10.99.99.61 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you may also need to clear the xlate for this entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's not clear from your config but what does access-list allownat do. It may be that this NAT takes effect before your nat 3 statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You haven't got any entries for .206 in your acl, are you going to add them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally speaking servers that you want to present to the outside should use static (inside,outside) ... statements rather than nat/global statements. Nat/global statements are more commonly used for dynamic NAT.&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, 06 Nov 2008 21:38:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125281#M893908</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-11-06T21:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: NAT issue</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125282#M893910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;Thanks for the assistance. &lt;/P&gt;&lt;P&gt;Removing the nat (inside) statement for that specific server worked.&lt;/P&gt;&lt;P&gt;My only concern is that I have other static entries for that server so when I inserted the &lt;/P&gt;&lt;P&gt;static (inside,outside) 172.16.199.206 10.99.99.61 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;entry i recieved a warning regarding their already being static entries, although it still inserted the line and works as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Nov 2008 22:29:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125282#M893910</guid>
      <dc:creator>joeduea67</dc:creator>
      <dc:date>2008-11-06T22:29:33Z</dc:date>
    </item>
    <item>
      <title>Re: NAT issue</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125283#M893912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should be alright because you are using a different public IP in your other static statement ie. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 172.16.199.207 smtp 10.99.99.61 smtp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you may want to check that your smtp still works but it should be fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you could do if you get problems is map the specific ports as you have done with the static statement above rather than just all ports eg.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp 172.16.199.206 www 10.99.99.61 www &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but it does depend how many ports you are allowing through to that server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Glad you got it working and appreciate the rating.&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, 06 Nov 2008 22:36:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/1125283#M893912</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-11-06T22:36:40Z</dc:date>
    </item>
  </channel>
</rss>

