<?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: How can it work in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932502#M917766</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;According your diagram&lt;/P&gt;&lt;P&gt;192.168.2.11 is in an outside segment&lt;/P&gt;&lt;P&gt;But the same network is attached to pix's inside interface. &lt;/P&gt;&lt;P&gt;so PIX do not support such configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Jun 2008 15:28:36 GMT</pubDate>
    <dc:creator>a.alekseev</dc:creator>
    <dc:date>2008-06-25T15:28:36Z</dc:date>
    <item>
      <title>How can it work</title>
      <link>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932501#M917765</link>
      <description>&lt;P&gt;Can 192.168.2.11 connect to Terminal Server on Mapped IP?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check the attachment!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:04:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932501#M917765</guid>
      <dc:creator>cscisco_admin</dc:creator>
      <dc:date>2019-03-11T13:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: How can it work</title>
      <link>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932502#M917766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;According your diagram&lt;/P&gt;&lt;P&gt;192.168.2.11 is in an outside segment&lt;/P&gt;&lt;P&gt;But the same network is attached to pix's inside interface. &lt;/P&gt;&lt;P&gt;so PIX do not support such configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jun 2008 15:28:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932502#M917766</guid>
      <dc:creator>a.alekseev</dc:creator>
      <dc:date>2008-06-25T15:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: How can it work</title>
      <link>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932503#M917767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks very much. This is what i needed to know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now if i change pix inside interface IP like 192.168.22.1 then what configuration is needed to allow 192.168.21.11 connect to my Terminal Server on 192.168.21.2 through the mapped public ip of pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2008 06:28:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932503#M917767</guid>
      <dc:creator>cscisco_admin</dc:creator>
      <dc:date>2008-06-26T06:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: How can it work</title>
      <link>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932504#M917768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need static NAT or PAT and access-list on outside interface that permits connetions to you Terminal Server's piblic ip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2008 04:34:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-can-it-work/m-p/932504#M917768</guid>
      <dc:creator>a.alekseev</dc:creator>
      <dc:date>2008-06-27T04:34:37Z</dc:date>
    </item>
  </channel>
</rss>

