<?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 [SOLVED] - PRISMA ACCESS GLOBALPROTECT - URUGUAY'S MOBILE USERS VPN ISSUE DUE REGION-PRIO AND REGION-MAPPING!! in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/solved-prisma-access-globalprotect-uruguay-s-mobile-users-vpn/m-p/1431140#M7614</link>
    <description>&lt;P&gt;Hello, LiveCommunity team!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I have created this post to share my experience with a &lt;STRONG&gt;GlobalProtect&lt;/STRONG&gt; issue affecting some users in &lt;STRONG&gt;Uruguay&lt;/STRONG&gt;, who are unable to connect to &lt;STRONG&gt;GlobalProtect&lt;/STRONG&gt; deployed across &lt;STRONG&gt;Prisma Access locations&lt;/STRONG&gt; (&lt;STRONG&gt;India West, US NorthWest, Chile&lt;/STRONG&gt;)—even with the app configuration (&lt;STRONG&gt;App-Setting&lt;/STRONG&gt;) adjusted to set the source region to "&lt;STRONG&gt;ANY&lt;/STRONG&gt;"!!&lt;BR /&gt;&lt;BR /&gt;Mobile Users in Uruguay attempting to connect to GlobalProtect are experiencing VPN issues, in response to which the GlobalProtect agent displays the error message: "&lt;STRONG&gt;The network connection is unreachable or the gateway is unresponsive. Check the network connection and reconnect.&lt;/STRONG&gt;" as shown below:&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Uruguay's Mobile User GlobalProtect Agent Error Message&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_1-1794933118167.png" style="width: 277px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100192i4085C4B3131CF62C/image-dimensions/277x299?v=v2" width="277" height="299" role="button" title="DanielSRomero_1-1794933118167.png" alt="DanielSRomero_1-1794933118167.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Even in the Prisma Access GlobalProtect application configuration settings, we set the "&lt;STRONG&gt;Source Region&lt;/STRONG&gt;" to "&lt;STRONG&gt;ANY&lt;/STRONG&gt;," but the issue with the VPN persists.:&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Prisma Access GlobalProtect App-Setting &amp;gt; External Gateways&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_3-1794934430433.png" style="width: 867px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100194i541216D263478738/image-dimensions/867x220?v=v2" width="867" height="220" role="button" title="DanielSRomero_3-1794934430433.png" alt="DanielSRomero_3-1794934430433.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;However, other Mobile Users in various countries are able to establish the VPN agent connection with Prisma Access GlobalProtect without any issues.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;This is the Prisma Access GlobalProtect topology:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Palo Alto Prisma Access GlobalProtect Topology&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_4-1794935918724.png" style="width: 869px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100197iA8D873A0C35115F0/image-dimensions/869x493?v=v2" width="869" height="493" role="button" title="DanielSRomero_4-1794935918724.png" alt="DanielSRomero_4-1794935918724.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;In the following section, I will share the troubleshooting steps, workarounds, and the root cause analysis (&lt;STRONG&gt;RCA&lt;/STRONG&gt;).&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Daniel Romero&lt;BR /&gt;Senior Network/Security Engineer&lt;BR /&gt;PANW Partner&lt;BR /&gt;YouTube:&amp;nbsp;&lt;STRONG&gt;@DanielRomeroNetSecurity&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Nov 2026 17:25:43 GMT</pubDate>
    <dc:creator>DanielS.Romero</dc:creator>
    <dc:date>2026-11-17T17:25:43Z</dc:date>
    <item>
      <title>[SOLVED] - PRISMA ACCESS GLOBALPROTECT - URUGUAY'S MOBILE USERS VPN ISSUE DUE REGION-PRIO AND REGION-MAPPING!!</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/solved-prisma-access-globalprotect-uruguay-s-mobile-users-vpn/m-p/1431140#M7614</link>
      <description>&lt;P&gt;Hello, LiveCommunity team!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I have created this post to share my experience with a &lt;STRONG&gt;GlobalProtect&lt;/STRONG&gt; issue affecting some users in &lt;STRONG&gt;Uruguay&lt;/STRONG&gt;, who are unable to connect to &lt;STRONG&gt;GlobalProtect&lt;/STRONG&gt; deployed across &lt;STRONG&gt;Prisma Access locations&lt;/STRONG&gt; (&lt;STRONG&gt;India West, US NorthWest, Chile&lt;/STRONG&gt;)—even with the app configuration (&lt;STRONG&gt;App-Setting&lt;/STRONG&gt;) adjusted to set the source region to "&lt;STRONG&gt;ANY&lt;/STRONG&gt;"!!&lt;BR /&gt;&lt;BR /&gt;Mobile Users in Uruguay attempting to connect to GlobalProtect are experiencing VPN issues, in response to which the GlobalProtect agent displays the error message: "&lt;STRONG&gt;The network connection is unreachable or the gateway is unresponsive. Check the network connection and reconnect.&lt;/STRONG&gt;" as shown below:&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Uruguay's Mobile User GlobalProtect Agent Error Message&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_1-1794933118167.png" style="width: 277px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100192i4085C4B3131CF62C/image-dimensions/277x299?v=v2" width="277" height="299" role="button" title="DanielSRomero_1-1794933118167.png" alt="DanielSRomero_1-1794933118167.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Even in the Prisma Access GlobalProtect application configuration settings, we set the "&lt;STRONG&gt;Source Region&lt;/STRONG&gt;" to "&lt;STRONG&gt;ANY&lt;/STRONG&gt;," but the issue with the VPN persists.:&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Prisma Access GlobalProtect App-Setting &amp;gt; External Gateways&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_3-1794934430433.png" style="width: 867px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100194i541216D263478738/image-dimensions/867x220?v=v2" width="867" height="220" role="button" title="DanielSRomero_3-1794934430433.png" alt="DanielSRomero_3-1794934430433.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;However, other Mobile Users in various countries are able to establish the VPN agent connection with Prisma Access GlobalProtect without any issues.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;This is the Prisma Access GlobalProtect topology:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Palo Alto Prisma Access GlobalProtect Topology&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_4-1794935918724.png" style="width: 869px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100197iA8D873A0C35115F0/image-dimensions/869x493?v=v2" width="869" height="493" role="button" title="DanielSRomero_4-1794935918724.png" alt="DanielSRomero_4-1794935918724.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;In the following section, I will share the troubleshooting steps, workarounds, and the root cause analysis (&lt;STRONG&gt;RCA&lt;/STRONG&gt;).&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Daniel Romero&lt;BR /&gt;Senior Network/Security Engineer&lt;BR /&gt;PANW Partner&lt;BR /&gt;YouTube:&amp;nbsp;&lt;STRONG&gt;@DanielRomeroNetSecurity&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 17:25:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/solved-prisma-access-globalprotect-uruguay-s-mobile-users-vpn/m-p/1431140#M7614</guid>
      <dc:creator>DanielS.Romero</dc:creator>
      <dc:date>2026-11-17T17:25:43Z</dc:date>
    </item>
    <item>
      <title>Re: [SOLVED] - PRISMA ACCESS GLOBALPROTECT - URUGUAY'S MOBILE USERS VPN ISSUE DUE REGION-PRIO AND REGION-MAPPING!!</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/solved-prisma-access-globalprotect-uruguay-s-mobile-users-vpn/m-p/1431193#M7615</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello, LiveCommunity team!&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;I share the troubleshooting,&amp;nbsp;&lt;SPAN&gt;workarounds, and the root cause analysis (&lt;/SPAN&gt;&lt;STRONG&gt;RCA&lt;/STRONG&gt;&lt;SPAN&gt;) of this particular Prisma Access GlobalProtect issue, where mobile users in Uruguay cannot connect to the gateways deployed in (&lt;STRONG&gt;India West, US NorthWest, Chile&lt;/STRONG&gt;) even with the app configuration (&lt;STRONG&gt;App-Setting&lt;/STRONG&gt;) adjusted to set the source region to "&lt;STRONG&gt;ANY&lt;/STRONG&gt;"!!&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT size="5"&gt;Troubleshooting Steps&lt;BR /&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;1- To verify the actual underlying issue, we ask the user to generate the GlobalProtect agent logs with &lt;STRONG&gt;dump level&lt;/STRONG&gt;.&lt;BR /&gt;&lt;BR /&gt;2- On the &lt;STRONG&gt;PanGPS.log file&lt;/STRONG&gt; we see the next messages where the GlobalProtect agent make a &lt;STRONG&gt;IP-to-Region&lt;/STRONG&gt; Mapping based on the user's source public IP address to connect to the faster Gateway first on the same Region.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;GLOBALPROTECT PANGPS.LOG&lt;/STRONG&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Debug(9214): 11/13/26 22:56:51:677 &lt;STRONG&gt;REGION-PRIO, region code is UY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Debug(17171): 11/13/26 22:56:51:677 &lt;STRONG&gt;REGION-PRIO, save region code UY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Debug( 407): 11/13/26 22:57:00:229 &lt;STRONG&gt;REGION-PRIO, no match at all, error&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Debug( 407): 11/13/26 22:57:00:229 &lt;STRONG&gt;REGION-PRIO, no match at all, error&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T9440)Debug( 724): 11/13/26 22:57:02:505 &lt;STRONG&gt;gateway 0 of india-west-centrode.123123123.gw.gpcloudservice.com is manual select only, will not be in rediscover list&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T9440)Debug( 691): 11/13/26 22:57:02:505 &lt;STRONG&gt;REGION-PRIO, gateway 1 is not selectable base on region&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T9440)Debug( 691): 11/13/26 22:57:02:505 &lt;STRONG&gt;REGION-PRIO, gateway 2 is not selectable base on region&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T9440)Debug( 759): 11/13/26 22:57:02:505 &lt;STRONG&gt;There is no gateway suitable to discovery&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T9440)Error(7835): 11/13/26 22:57:02:505 NetworkDiscoverThread: failed to discover external network.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T9440)Debug(7859): 11/13/26 22:57:02:505 &lt;STRONG&gt;Network discovery failed, set error as The network connection is unreachable or the gateway is unresponsive. Check the network connection and reconnec&lt;/STRONG&gt;t.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T9440)Debug(8931): 11/13/26 22:57:02:505 &lt;STRONG&gt;--Set state to Disconnected&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;We see GlobalProtect assign a &lt;FONT color="#000000"&gt;&lt;STRONG&gt;priority -2&lt;/STRONG&gt;&lt;/FONT&gt; for the Gateways available at&amp;nbsp;&lt;STRONG&gt;India West,&amp;nbsp;US Northeast and&amp;nbsp;Chile&lt;/STRONG&gt;, it means the GP agent will never try to connect to that Gateways, as shown below:&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;INDIA WEST GATEWAYS REGION MATCHING AND PRIORITY&lt;BR /&gt;&lt;/STRONG&gt;&lt;EM&gt;(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, after search for exact region match, i=10, m_nRegions=10&lt;BR /&gt;&lt;/STRONG&gt;(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, no exact match, search for ANY&lt;BR /&gt;&lt;/STRONG&gt;(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, no match at all, error&lt;BR /&gt;&lt;/STRONG&gt;(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, regioncode=UY, return priority -2, bManual=0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;US NORTHWEST GATEWAYS REGION MATCHING AND PRIORITY&lt;/STRONG&gt;&lt;BR /&gt;(&lt;EM&gt;P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, after search for exact region match, i=16, m_nRegions=16&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, no exact match, search for ANY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, no match at all, error&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, regioncode=UY, return priority -2, bManual=0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;CHILE GATEWAYS REGION MATCHING AND PRIORITY&lt;/STRONG&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, after search for exact region match, i=4, m_nRegions=4&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, no exact match, search for ANY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, no match at all, error&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, regioncode=UY, return priority -2, bManual=0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Root Cause Analysis (RCA)&lt;BR /&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;Based on these logs, we know that the GP agent evaluates whether the user's region &lt;STRONG&gt;Uruguay (UY)&amp;nbsp;&lt;/STRONG&gt;matches the available regions implemented/supported at each Prisma Access location (&lt;STRONG&gt;India West, US Northwest, and Chile&lt;/STRONG&gt;); however, none of these locations include a region that matches with the user's region&amp;nbsp;&lt;STRONG&gt;Uruguay (UY)&lt;/STRONG&gt;.&lt;BR /&gt;&lt;BR /&gt;Even if the source region is set to "&lt;STRONG&gt;ANY&lt;/STRONG&gt;" in the App-Setting rule, the issue persists; this is because there is an underlying list of regions ("&lt;STRONG&gt;countries&lt;/STRONG&gt;") available for each Prisma Access location. If the actual user's source region does not match any of the regions available in that list for a given Prisma Access location, the &lt;STRONG&gt;GlobalProtect (GP)&lt;/STRONG&gt; agent assigns a default &lt;STRONG&gt;priority of -2&lt;/STRONG&gt; to prevent the use of those Gateways.&lt;BR /&gt;&lt;STRONG&gt;&lt;BR /&gt;GLOBALPROTECT REGION PRIORITY TABLE&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_0-1794960985982.png" style="width: 554px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100214iF6D9D73CF1746C7F/image-dimensions/554x256?v=v2" width="554" height="256" role="button" title="DanielSRomero_0-1794960985982.png" alt="DanielSRomero_0-1794960985982.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;Palo Alto Networks Prisma Access offers over 100 locations across 76 countries to accommodate worldwide deployments and provide a localized experience.&amp;nbsp;These regions and locations are dynamically updated.&lt;BR /&gt;&lt;/SPAN&gt;&lt;BR /&gt;This entire design addresses issues of performance, redundancy, and internal considerations.&amp;nbsp;&lt;SPAN&gt;These underlying lists are dynamic and can be updated.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Palo Alto Networks&amp;nbsp;&lt;SPAN&gt;strongly recommends enabling at least one of the regional and global fallback locations during mobile user onboarding for redundancy in case the in-country location becomes unavailable.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Source:&amp;nbsp;&lt;A href="https://www.paloaltonetworks.com/resources/guides/sase-sec-int-mobile-users-tm-design" target="_blank" rel="noopener"&gt;Securing Internet Access for Mobile Users by Using Tunnel Mode: Design Guide - Palo Alto Networks&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Solution and Workarounds&lt;BR /&gt;&lt;/STRONG&gt;&lt;/FONT&gt;As a solution we must deployed a new Prisma Access Location at Uruguay, then the GP agent was able to connect to the Uruguay Gateway!!&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;PRISMA ACCESS GLOBALPROTECT ENABLE NEW URUGUAY LOCATION&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_1-1794958672669.png" style="width: 835px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100210iB50AAEBCB4132495/image-dimensions/835x311?v=v2" width="835" height="311" role="button" title="DanielSRomero_1-1794958672669.png" alt="DanielSRomero_1-1794958672669.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Note&lt;/STRONG&gt;: After we enable the new&amp;nbsp;&lt;STRONG&gt;Uruguay&lt;/STRONG&gt; location we need to activate the new Egress IPs and push the configuration to the changes take effect!!&lt;BR /&gt;&lt;BR /&gt;After this, the&amp;nbsp;&lt;STRONG&gt;PanGPS.log&lt;/STRONG&gt; file shows the underlying list with the exact region Uruguay&amp;nbsp;&lt;STRONG&gt;UY&lt;/STRONG&gt; available for the Uruguay users!&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;GLOBALPROTECT PANGPS.LOG&lt;/STRONG&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, regioncode=UY, return priority -2, bManual=0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 886): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, found new tag, we use new logic&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 899): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, gateway 3(Uruguay), 0, region = UY, priority = 1, portalRegion=UY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 909): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, get configuration base on region, region code=UY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 355): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, regionCode=UY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 380): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, i = 0, region code=UY, region=UY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, after search for exact region match, i=0, m_nRegions=1&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 &lt;STRONG&gt;REGION-PRIO, regioncode=UY, return priority 1, bManual=0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump (6604): 11/13/26 23:47:20:549 &lt;STRONG&gt;gateway chile-centrode.123456.gw.gpcloudservice.com priority is 1&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump ( 703): 11/13/26 23:47:20:549 &lt;STRONG&gt;pg, pg is , gateway ip is chile-centrode.123456.gw.gpcloudservice.com, remotehoststr=NULL, remotehoststrv6=, prefergatewaysource=0, isprelogonInProcess is 0&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump ( 741): 11/13/26 23:47:20:549 &lt;STRONG&gt;start the 0 thread for gateway chile-centrode.123456.gw.gpcloudservice.com&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T4884)Dump (6030): 11/13/26 23:47:20:549 &lt;STRONG&gt;Process gateway: host chile-centrode.123456.gw.gpcloudservice.com, description Uruguay&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 &lt;STRONG&gt;ignore gateway india-west-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 &lt;STRONG&gt;ignore gateway us-east-g-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 &lt;STRONG&gt;ignore gateway chile-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump (6604): 11/13/26 23:47:20:732 &lt;STRONG&gt;gateway chile-centrode.123456.gw.gpcloudservice.com priority is 1&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Dump (1306): 11/13/26 23:47:20:732 &lt;STRONG&gt;REGION-PRIO, gateway chile-centrode.123456.gw.gpcloudservice.com get priority 1 for region&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Debug(1430): 11/13/26 23:47:20:732 &lt;STRONG&gt;gateway Uruguay (chile-centrode.123456.gw.gpcloudservice.com), priority=1, duration=80 ms, assign 20 as its weight&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Info (1469): 11/13/26 23:47:20:732 &lt;STRONG&gt;CPanGatewayList::PickGatewayBaseOnWeight, PAN_NEW_GATEWAY_SELECTOR, chose prefered gateway index =3, gateway is Uruguay&lt;BR /&gt;&lt;/STRONG&gt;(P4420-T17000)Debug(4064): 11/13/26 23:47:21:737 &lt;STRONG&gt;REGION-PRIO, gateway region code is UY&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(P4420-T17000)Debug(4096): 11/13/26 23:47:21:737 &lt;/EM&gt;&lt;STRONG&gt;&lt;EM&gt;REGION-PRIO, portal and gateway have same region code&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;Palo Alto Prisma Access GlobalProtect Topology New Uruguay Location&lt;/FONT&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_2-1794959493242.png" style="width: 815px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100211i5A9FB666C86AA504/image-dimensions/815x471?v=v2" width="815" height="471" role="button" title="DanielSRomero_2-1794959493242.png" alt="DanielSRomero_2-1794959493242.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Possible Workaround&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Additionally, as an alternative solution if deploy a new Prisma Access Location it's not possible, by adding the source user "&lt;STRONG&gt;Uruguay (UY)&lt;/STRONG&gt;" explicitly as a source region within the application setting rules (&lt;STRONG&gt;App-Setting&lt;/STRONG&gt;), alongside "&lt;STRONG&gt;gpcloudservice.com"&lt;/STRONG&gt;&amp;nbsp;or a specific Gateway FQDN it appears that this force the underlying list to permit the users to connect to those Gateways. (&lt;STRONG&gt;We need to test it to confirm this workaround&lt;/STRONG&gt;)&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":beaming_face_with_smiling_eyes:"&gt;😁&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;The App-Setting rules that include more specific source regions take precedence over a rule with source region defined as "&lt;STRONG&gt;ANY&lt;/STRONG&gt;".&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Prisma Access GlobalProtect App-Setting &amp;gt; External Gateways&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielSRomero_4-1794959920461.png" style="width: 830px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/100213iF7CFBC88DCB5180D/image-dimensions/830x221?v=v2" width="830" height="221" role="button" title="DanielSRomero_4-1794959920461.png" alt="DanielSRomero_4-1794959920461.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the rule in the application settings is defined with the origin region set to "&lt;STRONG&gt;ANY&lt;/STRONG&gt;," this implies that the selection of the region or gateway location will be based on the dynamic underlying list of supported/available regions of each location.&lt;BR /&gt;&lt;BR /&gt;If you have any questions or comments, let me know in the comments section!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Thank you for your time, and I hope this information is helpful in your daily cybersecurity work. I would greatly appreciate your support by liking or accepting this as a useful post; it would help me a lot in becoming a CyberElite!&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;Best Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Daniel Romero&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Senior Network/Security Engineer&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PANW Partner&lt;BR /&gt;&lt;/SPAN&gt;YouTube:&amp;nbsp;&lt;STRONG&gt;@DanielRomeroNetSecurity&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2026 00:20:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/solved-prisma-access-globalprotect-uruguay-s-mobile-users-vpn/m-p/1431193#M7615</guid>
      <dc:creator>DanielS.Romero</dc:creator>
      <dc:date>2026-11-18T00:20:49Z</dc:date>
    </item>
  </channel>
</rss>

