<?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 hostname for client endpoints in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/290921#M77207</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/116419"&gt;@Drew-Gilman&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;So is my understanding correct that you don't have DNS entries for these IPs? If that's the case, the only way you can work around this is by utilizing the hosts file to map a hostname to the IP address; as the agent will then actually know where the traffic is actually supposed to go.&lt;/P&gt;</description>
    <pubDate>Wed, 02 Oct 2019 17:56:02 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2019-10-02T17:56:02Z</dc:date>
    <item>
      <title>GlobalProtect Portal hostname for client endpoints</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/290819#M77189</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've been trying to find out if it's possible to assign a hostname to a portal so that clients' portal list on their workstations have hostnames rather than IP addresses. I work in an environment where IP address for different "sites" are similar, so it can be difficult for them to remember which IP goes to a site.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have this functionality with Cisco ASA's by creating an XML document to attach as a profile for the Anyconnect clients.. Do PA's have this functionality?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm working with PA-220's and PA-220R's running 9.0.X.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2019 21:27:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/290819#M77189</guid>
      <dc:creator>Drew-Gilman</dc:creator>
      <dc:date>2019-10-01T21:27:08Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal hostname for client endpoints</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/290921#M77207</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/116419"&gt;@Drew-Gilman&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;So is my understanding correct that you don't have DNS entries for these IPs? If that's the case, the only way you can work around this is by utilizing the hosts file to map a hostname to the IP address; as the agent will then actually know where the traffic is actually supposed to go.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2019 17:56:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/290921#M77207</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-10-02T17:56:02Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal hostname for client endpoints</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/290949#M77210</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I would say utilize and IP space that does not overlap, then create your DNS entry. Then perhaps use the following to help you deploy/modify the client settings?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/8-0/globalprotect-admin/globalprotect-clients/deploy-agent-settings-transparently.html#" target="_blank"&gt;https://docs.paloaltonetworks.com/globalprotect/8-0/globalprotect-admin/globalprotect-clients/deploy-agent-settings-transparently.html#&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2019 18:47:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/290949#M77210</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-10-02T18:47:20Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Portal hostname for client endpoints</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/292142#M77360</link>
      <description>&lt;P&gt;Thank you both for your response!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That is correct, and we will not be purchasing domain's for these sites.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hopefully, in newer versions of GP, they'll make it so you don't have to own a domain in order to nickname the portals in the session list...&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2019 14:01:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/globalprotect-portal-hostname-for-client-endpoints/m-p/292142#M77360</guid>
      <dc:creator>Drew-Gilman</dc:creator>
      <dc:date>2019-10-09T14:01:45Z</dc:date>
    </item>
  </channel>
</rss>

