<?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 E84.x DNS server issue from sk171378 in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/E84-x-DNS-server-issue-from-sk171378/m-p/108294#M9287</link>
    <description>&lt;P&gt;Yesterday a customer contacted me about this issue with his E84.30 Win10 Enterprise VPN clients and received a fixed build of E84.30. Manual workaround on client is possible, but as it has to be performed for every user it is much easier to roll out a new client version instead. TAC in chat needed some 20 minutes to create an SFTP folder with the fixed client.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jan 2021 12:38:03 GMT</pubDate>
    <dc:creator>G_W_Albrecht</dc:creator>
    <dc:date>2021-01-20T12:38:03Z</dc:date>
    <item>
      <title>E84.x DNS server issue from sk171378</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/E84-x-DNS-server-issue-from-sk171378/m-p/108294#M9287</link>
      <description>&lt;P&gt;Yesterday a customer contacted me about this issue with his E84.30 Win10 Enterprise VPN clients and received a fixed build of E84.30. Manual workaround on client is possible, but as it has to be performed for every user it is much easier to roll out a new client version instead. TAC in chat needed some 20 minutes to create an SFTP folder with the fixed client.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2021 12:38:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/E84-x-DNS-server-issue-from-sk171378/m-p/108294#M9287</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2021-01-20T12:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: E84.x DNS server issue from sk171378</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/E84-x-DNS-server-issue-from-sk171378/m-p/108362#M9288</link>
      <description>&lt;P&gt;Believe we are going to release an updated client E84.40 that will also have this fix&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2021 04:57:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/E84-x-DNS-server-issue-from-sk171378/m-p/108362#M9288</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-01-21T04:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: E84.x DNS server issue from sk171378</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/E84-x-DNS-server-issue-from-sk171378/m-p/108417#M9289</link>
      <description>&lt;P&gt;I myself have experienced some DNS weirdness in Mac E84.30 on Big Sur.&amp;nbsp; Just yesterday DNS requests (i.e. nslookup) to one of our datacenter hosts did not resolve on my Mac, but the same nslookup command worked for other DC hosts.&amp;nbsp; In the past rebooting my Mac has resolved the issue.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2021 15:25:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/E84-x-DNS-server-issue-from-sk171378/m-p/108417#M9289</guid>
      <dc:creator>udp443</dc:creator>
      <dc:date>2021-01-21T15:25:51Z</dc:date>
    </item>
  </channel>
</rss>

