<?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: Symantec real time scanning not recognized after upgrading to globalprotect 5.0.5 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/300749#M78562</link>
    <description>&lt;P&gt;To troubleshoot the issue, you can check if HIP Match is taking place as expected, by checking the HIP match logs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can also check the full HIP Report by running the below command from CLI:&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;gt; debug user-id dump hip-report ip &amp;lt;IP-Address&amp;gt; user &amp;lt;Username&amp;gt; computer &amp;lt;Computer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;To know exactly what to type for the needed fields, you can navigate to "Network &amp;gt; GlobalProtect &amp;gt; Gateways", and then click on "Remote Users", identify the user and fill in according to the below mapping:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;lt;IP-Address&amp;gt; --&amp;gt; Private IP&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;lt;Username&amp;gt; --&amp;gt; Primary Username&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;lt;Computer&amp;gt; --&amp;gt; Computer&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;I hope this helps!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Nov 2019 10:17:28 GMT</pubDate>
    <dc:creator>aamarin</dc:creator>
    <dc:date>2019-11-26T10:17:28Z</dc:date>
    <item>
      <title>Symantec real time scanning not recognized after upgrading to globalprotect 5.0.5</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/299796#M78419</link>
      <description>&lt;P&gt;Anybody else having problems with GP clients not connecting after upgrading globalprotect to 5.0.5? It looks like 'real time scanning' feature of our Symantec endpoint protection is not being recognized and therefore HIP profile not matching.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2019 22:04:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/299796#M78419</guid>
      <dc:creator>Mpizarro1</dc:creator>
      <dc:date>2019-11-20T22:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec real time scanning not recognized after upgrading to globalprotect 5.0.5</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/300749#M78562</link>
      <description>&lt;P&gt;To troubleshoot the issue, you can check if HIP Match is taking place as expected, by checking the HIP match logs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can also check the full HIP Report by running the below command from CLI:&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;gt; debug user-id dump hip-report ip &amp;lt;IP-Address&amp;gt; user &amp;lt;Username&amp;gt; computer &amp;lt;Computer&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;To know exactly what to type for the needed fields, you can navigate to "Network &amp;gt; GlobalProtect &amp;gt; Gateways", and then click on "Remote Users", identify the user and fill in according to the below mapping:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;lt;IP-Address&amp;gt; --&amp;gt; Private IP&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;lt;Username&amp;gt; --&amp;gt; Primary Username&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;lt;Computer&amp;gt; --&amp;gt; Computer&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;I hope this helps!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2019 10:17:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/300749#M78562</guid>
      <dc:creator>aamarin</dc:creator>
      <dc:date>2019-11-26T10:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec real time scanning not recognized after upgrading to globalprotect 5.0.5</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/301084#M78620</link>
      <description>&lt;P&gt;Thank you Aamarin. I already checked HIP and debug hip commands. It seems like we are running into a bug. TAC is investigating, but I was curious if anybody else has experienced similar.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 17:05:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/301084#M78620</guid>
      <dc:creator>Mpizarro1</dc:creator>
      <dc:date>2019-11-27T17:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: Symantec real time scanning not recognized after upgrading to globalprotect 5.0.5</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/309229#M80157</link>
      <description>&lt;P&gt;I am facing the same issue on GP client 5.0.6, I am running Symantec 14.2 version on my Mac&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2020 19:19:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/symantec-real-time-scanning-not-recognized-after-upgrading-to/m-p/309229#M80157</guid>
      <dc:creator>RPendela</dc:creator>
      <dc:date>2020-02-03T19:19:06Z</dc:date>
    </item>
  </channel>
</rss>

