<?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 Portal does not respond on DHCP addressed interface in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2195#M1631</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My device is working well.&lt;/P&gt;&lt;P&gt;This is what I configured on my PA-200 v4.1.8&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ethernet1/1 is configured as DHCP client.&lt;/P&gt;&lt;P&gt;In GP Portal settings, I only select Interface and leave IP address as 'none'.&lt;/P&gt;&lt;P&gt;In GP Gateway settings, I configured same as above on Tunnel Gateway Address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just be careful, you have to enter exact IP address that eth1/1 will be assigned in external gateway list.&lt;/P&gt;&lt;P&gt;If you use dynamic IP address, you might need FQDN instead.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Emr&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Oct 2012 06:41:45 GMT</pubDate>
    <dc:creator>emr_1</dc:creator>
    <dc:date>2012-10-15T06:41:45Z</dc:date>
    <item>
      <title>GlobalProtect Portal does not respond on DHCP addressed interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2194#M1630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have don't extensive testing and discovered that if a GlobalProtect Portal interface is addressed via DHCP it does not respond to HTTPS requests. It only responds if the Portal interface has a Static IP Address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone please help with why?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 14 Oct 2012 23:25:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2194#M1630</guid>
      <dc:creator>jwolach</dc:creator>
      <dc:date>2012-10-14T23:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal does not respond on DHCP addressed interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2195#M1631</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My device is working well.&lt;/P&gt;&lt;P&gt;This is what I configured on my PA-200 v4.1.8&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ethernet1/1 is configured as DHCP client.&lt;/P&gt;&lt;P&gt;In GP Portal settings, I only select Interface and leave IP address as 'none'.&lt;/P&gt;&lt;P&gt;In GP Gateway settings, I configured same as above on Tunnel Gateway Address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just be careful, you have to enter exact IP address that eth1/1 will be assigned in external gateway list.&lt;/P&gt;&lt;P&gt;If you use dynamic IP address, you might need FQDN instead.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Emr&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Oct 2012 06:41:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2195#M1631</guid>
      <dc:creator>emr_1</dc:creator>
      <dc:date>2012-10-15T06:41:45Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal does not respond on DHCP addressed interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2196#M1632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Emr,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I apologize, I wasn't very clear in my previous post.&amp;nbsp; I was so frustrated that I forgot a few items.&amp;nbsp; You're correct, with the configuration you describe, yes, it does work however, only from the outside.&amp;nbsp; Internal users still cannot connect to the GP Portal address when it is a DHCP IP address on the Portal interface.&amp;nbsp; The other configuration I was trying was NATting GP Portal &amp;amp; Gateway connections to a Loopback interface.&amp;nbsp; It works perfectly if the Public interface is a static IP address.&amp;nbsp; Once I change it to a DHCP address, it will not respond to Portal or Gateway connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx,&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Oct 2012 11:37:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2196#M1632</guid>
      <dc:creator>jwolach</dc:creator>
      <dc:date>2012-10-15T11:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal does not respond on DHCP addressed interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2197#M1633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Emr,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can your GP agents connect to the Portal when they are on the local network or are they using Cached Portal?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx,&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Oct 2012 14:23:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2197#M1633</guid>
      <dc:creator>jwolach</dc:creator>
      <dc:date>2012-10-15T14:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal does not respond on DHCP addressed interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2198#M1634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tested on my unit.&lt;/P&gt;&lt;P&gt;As you say, I can't access to outside I/F from inside even I configure no NAT rule.&lt;/P&gt;&lt;P&gt;Hence if enable ssl management on outside I/F, I could access to &lt;A href="https://outside/"&gt;https://outside&lt;/A&gt; IP address:4443/.&lt;/P&gt;&lt;P&gt;This means it might be a bug.&lt;/P&gt;&lt;P&gt;I think we need to open a case for further investigation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Emr&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Oct 2012 10:55:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2198#M1634</guid>
      <dc:creator>emr_1</dc:creator>
      <dc:date>2012-10-17T10:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal does not respond on DHCP addressed interface</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2199#M1635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I believe this is a bug too.&amp;nbsp; Maybe a fix will also fix the issue I'm having with NATting my GP Portal &amp;amp; Gateway to a loopback interface when the Ext interface is dynamically addressed.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Oct 2012 11:44:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-does-not-respond-on-dhcp-addressed/m-p/2199#M1635</guid>
      <dc:creator>jwolach</dc:creator>
      <dc:date>2012-10-17T11:44:46Z</dc:date>
    </item>
  </channel>
</rss>

