<?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 Global Objects in PIX 7.2 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/global-objects-in-pix-7-2/m-p/745622#M964342</link>
    <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  I am seeing a unique problem whenever I create Network Object group in PIX firewall an other Network Object group with same name_ref is also created on the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, I created a group called webserver group an new group called wbserver_ref_1 was also created&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I narrowed down the issue. It happens only for groups which have NATted hosts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The webserver group contains hosts with private IP addresses and webserver_ref_1 group contains the same hosts with their public addresses as members.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I overcome this issue. Should I create only the Public IP addresses in the network group or should I rename the internal hosts to different group id.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chandru&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 11:02:50 GMT</pubDate>
    <dc:creator>csaravanan</dc:creator>
    <dc:date>2019-03-11T11:02:50Z</dc:date>
    <item>
      <title>Global Objects in PIX 7.2</title>
      <link>https://community.cisco.com/t5/network-security/global-objects-in-pix-7-2/m-p/745622#M964342</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  I am seeing a unique problem whenever I create Network Object group in PIX firewall an other Network Object group with same name_ref is also created on the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, I created a group called webserver group an new group called wbserver_ref_1 was also created&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I narrowed down the issue. It happens only for groups which have NATted hosts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The webserver group contains hosts with private IP addresses and webserver_ref_1 group contains the same hosts with their public addresses as members.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I overcome this issue. Should I create only the Public IP addresses in the network group or should I rename the internal hosts to different group id.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chandru&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:02:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/global-objects-in-pix-7-2/m-p/745622#M964342</guid>
      <dc:creator>csaravanan</dc:creator>
      <dc:date>2019-03-11T11:02:50Z</dc:date>
    </item>
    <item>
      <title>Re: Global Objects in PIX 7.2</title>
      <link>https://community.cisco.com/t5/network-security/global-objects-in-pix-7-2/m-p/745623#M964344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Refer to the secrion "How Object Grouping Works " in the folllowing document for configuration and operation related&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/traffic.html#wp1042213" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/traffic.html#wp1042213&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Aug 2007 19:08:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/global-objects-in-pix-7-2/m-p/745623#M964344</guid>
      <dc:creator>mmellet</dc:creator>
      <dc:date>2007-08-31T19:08:17Z</dc:date>
    </item>
  </channel>
</rss>

