<?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: Unable to Access Palo Alto Firewall via Public IP (Used as GlobalProtect Gateway) in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unable-to-access-palo-alto-firewall-via-public-ip-used-as/m-p/1230085#M5933</link>
    <description>&lt;P&gt;Palo changes management port to 4443 if GlobalProtect is enabled on same interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm8SCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm8SCAS&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is highly advisable not to open management port to public Internet due security reasons.&lt;/P&gt;</description>
    <pubDate>Mon, 26 May 2025 12:49:48 GMT</pubDate>
    <dc:creator>Raido_Rattameister</dc:creator>
    <dc:date>2025-05-26T12:49:48Z</dc:date>
    <item>
      <title>Unable to Access Palo Alto Firewall via Public IP (Used as GlobalProtect Gateway)</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unable-to-access-palo-alto-firewall-via-public-ip-used-as/m-p/1230083#M5932</link>
      <description>&lt;P data-start="208" data-end="215"&gt;Hi all,&lt;/P&gt;
&lt;P data-start="217" data-end="385"&gt;I'm facing an issue where I'm unable to access my Palo Alto firewall using its public (live) IP address. The same IP is configured as the &lt;STRONG data-start="355" data-end="384"&gt;GlobalProtect VPN gateway&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P data-start="387" data-end="570"&gt;As soon as I set the live IP as the GlobalProtect gateway, I can no longer access the firewall's management interface via that IP. It was working before assigning it to GlobalProtect.&lt;/P&gt;
&lt;P data-start="572" data-end="721"&gt;Is this expected behavior, or is there a workaround that would allow me to manage the firewall while also using the same public IP for GlobalProtect?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P data-start="723" data-end="777"&gt;Any advice or configuration tips would be appreciated!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P data-start="779" data-end="811"&gt;Thanks in advance,&lt;BR data-start="797" data-end="800" /&gt;Chirag Chudasama&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 12:05:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/unable-to-access-palo-alto-firewall-via-public-ip-used-as/m-p/1230083#M5932</guid>
      <dc:creator>ChiragChudasama</dc:creator>
      <dc:date>2025-05-26T12:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Access Palo Alto Firewall via Public IP (Used as GlobalProtect Gateway)</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unable-to-access-palo-alto-firewall-via-public-ip-used-as/m-p/1230085#M5933</link>
      <description>&lt;P&gt;Palo changes management port to 4443 if GlobalProtect is enabled on same interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm8SCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm8SCAS&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is highly advisable not to open management port to public Internet due security reasons.&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 12:49:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/unable-to-access-palo-alto-firewall-via-public-ip-used-as/m-p/1230085#M5933</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2025-05-26T12:49:48Z</dc:date>
    </item>
  </channel>
</rss>

