<?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: Global Protect certificate error in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-certificate-error/m-p/133662#M47241</link>
    <description>&lt;P&gt;We were using GProtect version 1.2.2 and it was working fine. We decided to upgrade GProtect to version 2.3.2. We created a new certificate with the same CN in order to solve it, but this is not working &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why is not working???&lt;/P&gt;</description>
    <pubDate>Tue, 20 Dec 2016 08:41:52 GMT</pubDate>
    <dc:creator>soporteseguridad</dc:creator>
    <dc:date>2016-12-20T08:41:52Z</dc:date>
    <item>
      <title>Global Protect certificate error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-certificate-error/m-p/133207#M47177</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are testing GProtect 2.3.2 version and its not working fine.&lt;/P&gt;&lt;P&gt;Debug GP client shows "&lt;SPAN&gt;WINHTTP CALLBACK_STATUS_FLAG_CERT_CN_INVALID".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The certificate is issued with the Common Name clientvpn.xxx.xxx, and this is the address of the portal.&lt;BR /&gt;&amp;nbsp;If instead of the DNS name of the portal, we put the IP address, the client warns that the CN of the certificate does not match, but allows to establish the connection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;how can we solve this problem??&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2016 09:28:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-certificate-error/m-p/133207#M47177</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2016-12-16T09:28:06Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect certificate error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-certificate-error/m-p/133229#M47181</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Think you getting this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/GlobalProtect-client-doesn-t-trust-GlobalProtect-Portal/ta-p/65915" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/GlobalProtect-client-doesn-t-trust-GlobalProtect-Portal/ta-p/65915&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thx,&lt;/P&gt;&lt;P&gt;Myky&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2016 11:17:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-certificate-error/m-p/133229#M47181</guid>
      <dc:creator>TranceforLife</dc:creator>
      <dc:date>2016-12-16T11:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect certificate error</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-certificate-error/m-p/133662#M47241</link>
      <description>&lt;P&gt;We were using GProtect version 1.2.2 and it was working fine. We decided to upgrade GProtect to version 2.3.2. We created a new certificate with the same CN in order to solve it, but this is not working &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why is not working???&lt;/P&gt;</description>
      <pubDate>Tue, 20 Dec 2016 08:41:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-certificate-error/m-p/133662#M47241</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2016-12-20T08:41:52Z</dc:date>
    </item>
  </channel>
</rss>

