<?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: GlobalProtect intrazone access in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334772#M230</link>
    <description>&lt;P&gt;No setting denying anything from the GP zone in this list of policies except default rule found at the end which is for interzone.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jun 2020 13:27:27 GMT</pubDate>
    <dc:creator>EmilySamolewicz</dc:creator>
    <dc:date>2020-06-23T13:27:27Z</dc:date>
    <item>
      <title>GlobalProtect intrazone access</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334184#M216</link>
      <description>&lt;P&gt;Is it possible to create a rule to allow certain intrazone traffic for GlobalProtect clients. E.g. so that client1 on GP can ping client2s GP interface. I tried creating a specific rule that would allow traffic from GlobalProtect security zone to GlobalProtect security zone but no luck. Is this type of functionality achievable with GlobalProtect?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jun 2020 20:25:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334184#M216</guid>
      <dc:creator>EmilySamolewicz</dc:creator>
      <dc:date>2020-06-18T20:25:26Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect intrazone access</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334192#M217</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If there is an clean up rule before default rules, which allows intrazone traffic. There shoud be a specific rule above cleanup rule in oreder to allow ping, icmp and trace route. You can try this allowing gp-zone to gp-zone; source as any and destination as any, service as application default and application any (to monitor what happens).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also check the windows firewall if windows firewall is on, host machines not reply ping request.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jun 2020 21:16:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334192#M217</guid>
      <dc:creator>upelister</dc:creator>
      <dc:date>2020-06-18T21:16:32Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect intrazone access</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334534#M228</link>
      <description>&lt;P&gt;Hi, I have tried this without success with the configuration show in the attached image. The source and destination address are the GlobalProtect subnet 10.10.1.0/24 which I can't imagine is a problem. Windows firewall is also set to allow this traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2020-06-22 at 12.57.01.png" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/26297i38C26791E7E65284/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot 2020-06-22 at 12.57.01.png" alt="Screenshot 2020-06-22 at 12.57.01.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2020 11:00:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334534#M228</guid>
      <dc:creator>EmilySamolewicz</dc:creator>
      <dc:date>2020-06-22T11:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect intrazone access</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334579#M229</link>
      <description>&lt;P&gt;This is showing policy 17. The count is zero. Do you have a policy before this that is denying gp &amp;nbsp; &amp;nbsp;Traffic.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2020 17:34:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334579#M229</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2020-06-22T17:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect intrazone access</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334772#M230</link>
      <description>&lt;P&gt;No setting denying anything from the GP zone in this list of policies except default rule found at the end which is for interzone.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 13:27:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334772#M230</guid>
      <dc:creator>EmilySamolewicz</dc:creator>
      <dc:date>2020-06-23T13:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect intrazone access</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334778#M231</link>
      <description>&lt;P&gt;ok so override the two default policies and log session start, don't bother forwarding logs.&lt;/P&gt;&lt;P&gt;then on the firewall you will see what is happening to the pings.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 13:34:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-intrazone-access/m-p/334778#M231</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2020-06-23T13:34:30Z</dc:date>
    </item>
  </channel>
</rss>

