<?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 Terminal server Cluster with asa in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110179#M395733</link>
    <description>&lt;P&gt;Hy there&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a problem with a terminal server cluster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an asa with an interface sided to the terminal server cluster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is when someone is trying to connect to the cluster this gives back the answer with an different IP so the asa drops the connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Client_source : 192.168.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TS_1 : 10.10.1.1&lt;/P&gt;&lt;P&gt;TS_2 : 10.10.1.2&lt;/P&gt;&lt;P&gt;TS_3 : 10.10.1.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IP asa&lt;/P&gt;&lt;P&gt;inside : 192.168.1.254&lt;/P&gt;&lt;P&gt;TS_int: 10.10.1.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the client 192.168.1.1 attacks the main IP of the TS cluster 10.10.1.1 this loadbalance and answers for example with the IP 10.10.1.2 or 10.10.1.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The asa drops the connection because it expect and answer from 10.10.1.1 not from other source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 00:22:07 GMT</pubDate>
    <dc:creator>ovidio.catrina</dc:creator>
    <dc:date>2019-03-12T00:22:07Z</dc:date>
    <item>
      <title>Terminal server Cluster with asa</title>
      <link>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110179#M395733</link>
      <description>&lt;P&gt;Hy there&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a problem with a terminal server cluster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an asa with an interface sided to the terminal server cluster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is when someone is trying to connect to the cluster this gives back the answer with an different IP so the asa drops the connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Client_source : 192.168.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TS_1 : 10.10.1.1&lt;/P&gt;&lt;P&gt;TS_2 : 10.10.1.2&lt;/P&gt;&lt;P&gt;TS_3 : 10.10.1.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IP asa&lt;/P&gt;&lt;P&gt;inside : 192.168.1.254&lt;/P&gt;&lt;P&gt;TS_int: 10.10.1.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the client 192.168.1.1 attacks the main IP of the TS cluster 10.10.1.1 this loadbalance and answers for example with the IP 10.10.1.2 or 10.10.1.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The asa drops the connection because it expect and answer from 10.10.1.1 not from other source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:22:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110179#M395733</guid>
      <dc:creator>ovidio.catrina</dc:creator>
      <dc:date>2019-03-12T00:22:07Z</dc:date>
    </item>
    <item>
      <title>Terminal server Cluster with asa</title>
      <link>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110180#M395734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Take a look at source NAT (SNAT). I beleive that will take care of the problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2012 14:44:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110180#M395734</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2012-11-12T14:44:53Z</dc:date>
    </item>
    <item>
      <title>Terminal server Cluster with asa</title>
      <link>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110181#M395737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeap I was thinking so, but isn't there another way, like some kind of asymetric routing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2012 14:50:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110181#M395737</guid>
      <dc:creator>ovidio.catrina</dc:creator>
      <dc:date>2012-11-12T14:50:23Z</dc:date>
    </item>
    <item>
      <title>Terminal server Cluster with asa</title>
      <link>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110182#M395739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;TCP Bypass may work as well-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b2d922.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b2d922.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2012 18:14:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/terminal-server-cluster-with-asa/m-p/2110182#M395739</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2012-11-12T18:14:37Z</dc:date>
    </item>
  </channel>
</rss>

