<?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 you are right, there is only in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682669#M191619</link>
    <description>&lt;P&gt;you are right, there is only one nat-statement per object.&lt;/P&gt;
&lt;P&gt;You need to configure three objects with different names but the same host-entry. Each object will get an individual nat-entry:&lt;/P&gt;

&lt;PRE&gt;
object network obj-192.168.3.60-16000
  host 192.168.3.60
  nat (dmz4,outside) static 7.3.232.220 service tcp 16000 16000

object network obj-192.168.3.60-16001
  host 192.168.3.60
  nat (dmz4,outside) static 7.3.232.220 service tcp 16001 16001

object network obj-192.168.3.60-5003
  host 192.168.3.60
  nat (dmz4,outside) static 7.3.232.220 service tcp 5003 5003&lt;/PRE&gt;</description>
    <pubDate>Wed, 13 May 2015 15:32:22 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2015-05-13T15:32:22Z</dc:date>
    <item>
      <title>nat conversion</title>
      <link>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682668#M191617</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I need to convert the following from 8.2 nat to 9.0&lt;/P&gt;&lt;P&gt;static (dmz4,outside) tcp 7.3.232.220 16000 192.168.3.60 16000 netmask 255.255.255.255&lt;BR /&gt;static (dmz4,outside) tcp 7.3.232.220 16001 192.168.3.60 16001 netmask 255.255.255.255&lt;BR /&gt;static (dmz4,outside) tcp 7.3.232.220 5003 192.168.3.60 5003 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;I thought I needed a static PAT as follows:&lt;/P&gt;&lt;P&gt;object network obj-192.168.3.60&lt;/P&gt;&lt;P&gt;host 192.168.3.60&lt;/P&gt;&lt;P&gt;nat (dmz4,outside) static 7.3.232.220 service tcp 16000&lt;/P&gt;&lt;P&gt;nat (dmz4,outside) static 7.3.232.220 service tcp 16001&lt;/P&gt;&lt;P&gt;nat (dmz4,outside) static 7.3.232.220 service tcp 5003&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But it seems I can only have one static int the object. Only the last nat is shown in the group.&lt;/P&gt;&lt;P&gt;How do I configure this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:55:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682668#M191617</guid>
      <dc:creator>mickyq</dc:creator>
      <dc:date>2019-03-12T05:55:50Z</dc:date>
    </item>
    <item>
      <title>you are right, there is only</title>
      <link>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682669#M191619</link>
      <description>&lt;P&gt;you are right, there is only one nat-statement per object.&lt;/P&gt;
&lt;P&gt;You need to configure three objects with different names but the same host-entry. Each object will get an individual nat-entry:&lt;/P&gt;

&lt;PRE&gt;
object network obj-192.168.3.60-16000
  host 192.168.3.60
  nat (dmz4,outside) static 7.3.232.220 service tcp 16000 16000

object network obj-192.168.3.60-16001
  host 192.168.3.60
  nat (dmz4,outside) static 7.3.232.220 service tcp 16001 16001

object network obj-192.168.3.60-5003
  host 192.168.3.60
  nat (dmz4,outside) static 7.3.232.220 service tcp 5003 5003&lt;/PRE&gt;</description>
      <pubDate>Wed, 13 May 2015 15:32:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682669#M191619</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-05-13T15:32:22Z</dc:date>
    </item>
    <item>
      <title>The auto-nat (putting the nat</title>
      <link>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682670#M191620</link>
      <description>&lt;P&gt;The auto-nat (putting the nat in the object) will only allow a single nat statement. &amp;nbsp;You can create the nats in the same fashion that you have them by creating separate nat statements in global config.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;object network obj-192.168.3.60&lt;/P&gt;&lt;P&gt;&amp;nbsp;host 192.168.3.60&lt;/P&gt;&lt;P&gt;&amp;nbsp;exit&lt;/P&gt;&lt;P&gt;object network obj-7.3.232.220&lt;/P&gt;&lt;P&gt;&amp;nbsp;host 7.3.232.220&lt;/P&gt;&lt;P&gt;&amp;nbsp;exit&lt;/P&gt;&lt;P&gt;object service tcp16000&lt;/P&gt;&lt;P&gt;&amp;nbsp;service tcp destination 160000&lt;/P&gt;&lt;P&gt;&amp;nbsp;exit&lt;/P&gt;&lt;P&gt;object service tcp16001&lt;/P&gt;&lt;P&gt;&amp;nbsp;service tcp destination 160001&lt;/P&gt;&lt;P&gt;&amp;nbsp;exit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;nat (dmz4,outside) source static obj-192.168.3.60&amp;nbsp; obj-7.3.232.220&amp;nbsp;service&amp;nbsp;tcp16000&amp;nbsp;tcp16000&lt;/P&gt;&lt;P&gt;nat (dmz4,outside) source static&amp;nbsp;obj-192.168.3.60&amp;nbsp;&amp;nbsp;obj-7.3.232.220&amp;nbsp;service&amp;nbsp;tcp16001&amp;nbsp;tcp16001&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2015 15:36:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682670#M191620</guid>
      <dc:creator>JEFF SPRADLING</dc:creator>
      <dc:date>2015-05-13T15:36:50Z</dc:date>
    </item>
    <item>
      <title>Thanks GuysI see theres two</title>
      <link>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682671#M191622</link>
      <description>&lt;P&gt;Thanks Guys&lt;/P&gt;&lt;P&gt;I see theres two solutions. I guess its just a case of where i want them in the nat table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 07:32:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682671#M191622</guid>
      <dc:creator>mickyq</dc:creator>
      <dc:date>2015-05-14T07:32:40Z</dc:date>
    </item>
    <item>
      <title>Yes, it's more or less a</title>
      <link>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682672#M191623</link>
      <description>&lt;P&gt;Yes, it's more or less a personal preference. I always configure it the way that all "regular" NAT goes to section 2 (which is auto-NAT or object-NAT). That is also the port-forwarding that you need.&lt;/P&gt;&lt;P&gt;In section 1 (the manual NAT which Jeff showed you) I only configure NAT-exemption and policy NAT.&lt;/P&gt;&lt;P&gt;In section 3 I only have my dynamic PAT (overload) for general Internet-access.&lt;/P&gt;&lt;P&gt;Configuring it that way keeps the NAT-table quite readable.&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 08:06:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-conversion/m-p/2682672#M191623</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-05-14T08:06:52Z</dc:date>
    </item>
  </channel>
</rss>

