<?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: Failed to Connect from Ubuntu using snx after configuration change in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Failed-to-Connect-from-Ubuntu-using-snx-after-configuration/m-p/156957#M6318</link>
    <description>&lt;P&gt;What version/JHF is on the gateway?&lt;BR /&gt;Has a TAC case been opened for this?&lt;/P&gt;</description>
    <pubDate>Sat, 10 Sep 2022 02:26:14 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2022-09-10T02:26:14Z</dc:date>
    <item>
      <title>Failed to Connect from Ubuntu using snx after configuration change</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Failed-to-Connect-from-Ubuntu-using-snx-after-configuration/m-p/156744#M6317</link>
      <description>&lt;P&gt;I had a working connection from Ubuntu Linux 20.04 using snx build&amp;nbsp;800008304.&lt;/P&gt;&lt;P&gt;After connection changes from the network team, that did not break Windows clients, I can no longer log in.&lt;/P&gt;&lt;P&gt;I am told, that protocols and ciphers have been disabled (e.g.&amp;nbsp;&lt;SPAN&gt;. TLS1.0, TLS1.1).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Any ideas, what I could change on the client side, mitigating that.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The relevant part in the client side log is:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] talkssl::client_handler: Returning OK!!!&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] ckpSSL_NegotiateStep: current state = before/connect initialization&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] ckpSSL_NegotiateStep: should retry.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] ckpSSL_NegotiateStep: current state = SSLv2/v3 read server hello A&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] SSL e stack&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] 7794:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:757&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] ckpSSL_NegotiateStep: Current step failed. Error is: 336032784&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] ckpSSL_fwasync_connected: no connections err -3&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] fwasync_end_conn: scheduling the end of connection 7&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] fwasync_do_end_conn: closing connection 7 (conn=8acc960)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] talkssl::end_handler: ending connection &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] snx_browser::Failure: entering with code: 1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] got link down!- exit&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[ 7794 -141844416]@leopoldstadt[7 Sep 14:28:20] snx: quit.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Any tips or ideas are highly appreciated.&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2022 12:30:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Failed-to-Connect-from-Ubuntu-using-snx-after-configuration/m-p/156744#M6317</guid>
      <dc:creator>informatom</dc:creator>
      <dc:date>2022-09-07T12:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Connect from Ubuntu using snx after configuration change</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Failed-to-Connect-from-Ubuntu-using-snx-after-configuration/m-p/156957#M6318</link>
      <description>&lt;P&gt;What version/JHF is on the gateway?&lt;BR /&gt;Has a TAC case been opened for this?&lt;/P&gt;</description>
      <pubDate>Sat, 10 Sep 2022 02:26:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Failed-to-Connect-from-Ubuntu-using-snx-after-configuration/m-p/156957#M6318</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-09-10T02:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Connect from Ubuntu using snx after configuration change</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Failed-to-Connect-from-Ubuntu-using-snx-after-configuration/m-p/157215#M6319</link>
      <description>&lt;P&gt;Thank you for the quick answer, meanwhile the network team reversed their changes and I can log in as before. So, I actually don't know.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 11:01:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Failed-to-Connect-from-Ubuntu-using-snx-after-configuration/m-p/157215#M6319</guid>
      <dc:creator>informatom</dc:creator>
      <dc:date>2022-09-14T11:01:10Z</dc:date>
    </item>
  </channel>
</rss>

