<?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 PIX to ASA Migration Problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-to-asa-migration-problem/m-p/768068#M984580</link>
    <description>&lt;P&gt;I have migrated out PIX 525 to the ASA appliance.  All went well except for the following problem.  I need to be able to see traffic on one of my DMZs by both the real, and the translated IP addresses.  The PIX allowd this but the ASA does not.  Desperate need of some help here...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas? &lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 10:43:19 GMT</pubDate>
    <dc:creator>jimb</dc:creator>
    <dc:date>2019-03-11T10:43:19Z</dc:date>
    <item>
      <title>PIX to ASA Migration Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-to-asa-migration-problem/m-p/768068#M984580</link>
      <description>&lt;P&gt;I have migrated out PIX 525 to the ASA appliance.  All went well except for the following problem.  I need to be able to see traffic on one of my DMZs by both the real, and the translated IP addresses.  The PIX allowd this but the ASA does not.  Desperate need of some help here...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas? &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:43:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-to-asa-migration-problem/m-p/768068#M984580</guid>
      <dc:creator>jimb</dc:creator>
      <dc:date>2019-03-11T10:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: PIX to ASA Migration Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-to-asa-migration-problem/m-p/768069#M984582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please post the error message and configuration so we can help determine what's going on.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2007 10:45:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-to-asa-migration-problem/m-p/768069#M984582</guid>
      <dc:creator>jgervia_2</dc:creator>
      <dc:date>2007-07-11T10:45:46Z</dc:date>
    </item>
    <item>
      <title>Re: PIX to ASA Migration Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-to-asa-migration-problem/m-p/768070#M984585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not an error.  On one of my DMZs I translate 172.16.x.x to 10.1.x.x.  When we had the PIX, we could access nodes on that DMZ by both addresses from the inside network.  When we migrated to the ASA, we can no longer hit the network by 10.1.x.x addresses and are forced to use the translated addresses, 172.16.x.x.  This is a problem because users have become dependent on both address spaces.  Strange but true.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2007 11:08:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-to-asa-migration-problem/m-p/768070#M984585</guid>
      <dc:creator>jimb</dc:creator>
      <dc:date>2007-07-11T11:08:03Z</dc:date>
    </item>
  </channel>
</rss>

