<?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: [Network location] - too long to check location in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/network-location-too-long-to-check-location/m-p/518699#M3041</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/199145"&gt;@Olivier-C&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a known limitation due to checkin times. The agent performs a heartbeat to the cloud every 5 minutes and hence agents which are not able to checkin on network change do it in the next heartbeat cycle. This is a known behaviour and the lag is intermittent for the same reason. The agent upon the next checkin realises the location difference upon DC connectivity test and applies the rules accordingly. The workaround for this is that you set the required permissive rules which is a priority at the top and that should facilitate faster times for the same. Further you can request our TAC team to support further for the same.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that answers your question!&lt;/P&gt;</description>
    <pubDate>Fri, 21 Oct 2022 09:56:53 GMT</pubDate>
    <dc:creator>neelrohit</dc:creator>
    <dc:date>2022-10-21T09:56:53Z</dc:date>
    <item>
      <title>[Network location] - too long to check location</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/network-location-too-long-to-check-location/m-p/518695#M3040</link>
      <description>&lt;P&gt;Hi community,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does somebody is using Cortex XDR - Network Localtion (from agent settings profile).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My problem is that the network location is too long, specifically when users comme back to our office from their own internet connection, internal profile takes about 2 minutes to change from external to internal.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;External = restricted firewall policy&lt;/P&gt;
&lt;P&gt;Internal = light FW policy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So logon scripts ... are timed out du to Cortex location too long to change.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have you tried this, how do you deal with network location changing time?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you !&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Olivier.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2022 08:58:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/network-location-too-long-to-check-location/m-p/518695#M3040</guid>
      <dc:creator>Olivier-C</dc:creator>
      <dc:date>2022-10-21T08:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: [Network location] - too long to check location</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/network-location-too-long-to-check-location/m-p/518699#M3041</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/199145"&gt;@Olivier-C&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a known limitation due to checkin times. The agent performs a heartbeat to the cloud every 5 minutes and hence agents which are not able to checkin on network change do it in the next heartbeat cycle. This is a known behaviour and the lag is intermittent for the same reason. The agent upon the next checkin realises the location difference upon DC connectivity test and applies the rules accordingly. The workaround for this is that you set the required permissive rules which is a priority at the top and that should facilitate faster times for the same. Further you can request our TAC team to support further for the same.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that answers your question!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2022 09:56:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/network-location-too-long-to-check-location/m-p/518699#M3041</guid>
      <dc:creator>neelrohit</dc:creator>
      <dc:date>2022-10-21T09:56:53Z</dc:date>
    </item>
  </channel>
</rss>

