<?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 using multiple PAT global address! in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/using-multiple-pat-global-address/m-p/1881122#M458228</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; i check asa,&amp;nbsp;&amp;nbsp; we config 3 pat global real internet ip address.&amp;nbsp;&amp;nbsp;&amp;nbsp; when customer visit a bank https web page.&amp;nbsp; ASA established 5 connection, but translate to 2 different internet ip address.&amp;nbsp; customer can't this https web page.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we tried to config another group. asa established 5 connection , but internal ip address was translated to one same ip address, the problem gone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i think it is loadbalance mechanism on bank web server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but how can i config on asa, the same internal ip address get same global internet ip address to avoid this situation&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Mar 2012 13:15:00 GMT</pubDate>
    <dc:creator>fly</dc:creator>
    <dc:date>2012-03-13T13:15:00Z</dc:date>
    <item>
      <title>using multiple PAT global address!</title>
      <link>https://community.cisco.com/t5/network-security/using-multiple-pat-global-address/m-p/1881121#M458220</link>
      <description>&lt;P&gt;we met a problerm.&lt;/P&gt;&lt;P&gt;we translate multiple segment of internal network address to multiple global internet address.&amp;nbsp;&amp;nbsp; we met some problem. when one computer visit a bank web page, it will open another https web page.&amp;nbsp; customer found some times this page can't visit successfully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; i think may be ASA translate https web page to another global internet address, because we using multiple global addree in one global. so bank network load balance to another server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; is this an issue&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; thank you!&lt;/P&gt;&lt;P&gt;tom&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:41:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-multiple-pat-global-address/m-p/1881121#M458220</guid>
      <dc:creator>fly</dc:creator>
      <dc:date>2019-03-11T22:41:22Z</dc:date>
    </item>
    <item>
      <title>using multiple PAT global address!</title>
      <link>https://community.cisco.com/t5/network-security/using-multiple-pat-global-address/m-p/1881122#M458228</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; i check asa,&amp;nbsp;&amp;nbsp; we config 3 pat global real internet ip address.&amp;nbsp;&amp;nbsp;&amp;nbsp; when customer visit a bank https web page.&amp;nbsp; ASA established 5 connection, but translate to 2 different internet ip address.&amp;nbsp; customer can't this https web page.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we tried to config another group. asa established 5 connection , but internal ip address was translated to one same ip address, the problem gone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i think it is loadbalance mechanism on bank web server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but how can i config on asa, the same internal ip address get same global internet ip address to avoid this situation&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2012 13:15:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-multiple-pat-global-address/m-p/1881122#M458228</guid>
      <dc:creator>fly</dc:creator>
      <dc:date>2012-03-13T13:15:00Z</dc:date>
    </item>
  </channel>
</rss>

