<?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: IPsec L2TP  with ClusterXL in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/IPsec-L2TP-with-ClusterXL/m-p/86689#M10334</link>
    <description>&lt;P&gt;The Take 196 solved the issue.&lt;/P&gt;</description>
    <pubDate>Fri, 29 May 2020 07:21:51 GMT</pubDate>
    <dc:creator>Yaroslav_Basenk</dc:creator>
    <dc:date>2020-05-29T07:21:51Z</dc:date>
    <item>
      <title>IPsec L2TP  with ClusterXL</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/IPsec-L2TP-with-ClusterXL/m-p/86389#M10332</link>
      <description>&lt;P&gt;Hi guys,&lt;BR /&gt;I am trying to configure a Windows IPsec \ L2TP (Pre-shared Key) client connection for&amp;nbsp; ClusterXL and for standalone gateways. Authentication through AD. I made all the settings by the SK140832. All vpn setting on ClusterXL and on others gateways are the same.&lt;/P&gt;&lt;P&gt;The older client support&amp;nbsp;must be enabled for AD-auth support&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AD-support.JPG" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/6240i4E6010D9BF96F966/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AD-support.JPG" alt="AD-support.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Other settings&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Global-Settings.JPG" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/6241iA46548F8764308C3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Global-Settings.JPG" alt="Global-Settings.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vpn-blade-settings.JPG" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/6242iDD06B412ED4ED9AF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vpn-blade-settings.JPG" alt="vpn-blade-settings.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the connection only works for standalone gateways. For ClusterXL, I see an error in the logs: “This IKE SA should be used only for L2TP. Probably a computer certificate. "&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;For ClusterXL:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="failed_login.JPG" style="width: 655px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/6239iBD79CF8BB53EA5E4/image-dimensions/655x370?v=v2" width="655" height="370" role="button" title="failed_login.JPG" alt="failed_login.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;For others standalone gateways - the connection is perfect&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Login.JPG" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/6243i2044587DDE8834FA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Login.JPG" alt="Login.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation"&gt;&lt;SPAN class=""&gt;Does anyone have an idea - why?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2020 17:36:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/IPsec-L2TP-with-ClusterXL/m-p/86389#M10332</guid>
      <dc:creator>Yaroslav_Basenk</dc:creator>
      <dc:date>2020-05-26T17:36:41Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec L2TP  with ClusterXL</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/IPsec-L2TP-with-ClusterXL/m-p/86413#M10333</link>
      <description>There were definitely some issues with L2TP previously: &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk145895" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk145895&lt;/A&gt;&lt;BR /&gt;Recommend applying the latest GA Jumbo Hotfix.&lt;BR /&gt;If you're still having an issued, best to engage with TAC.</description>
      <pubDate>Wed, 27 May 2020 00:06:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/IPsec-L2TP-with-ClusterXL/m-p/86413#M10333</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-05-27T00:06:03Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec L2TP  with ClusterXL</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/IPsec-L2TP-with-ClusterXL/m-p/86689#M10334</link>
      <description>&lt;P&gt;The Take 196 solved the issue.&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2020 07:21:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/IPsec-L2TP-with-ClusterXL/m-p/86689#M10334</guid>
      <dc:creator>Yaroslav_Basenk</dc:creator>
      <dc:date>2020-05-29T07:21:51Z</dc:date>
    </item>
  </channel>
</rss>

