<?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: Global Protect - ip address for portal web service restricts visitors by their ip address - WHY? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-ip-address-for-portal-web-service-restricts/m-p/16038#M11716</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The IP address that you select is actually based on the interface that you have selected. So its actually a single IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From your description that you are able to connect on the same subnet but not on a different subnet tells me that you have a routing issue. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have default route or a static route with 36.12.0.0/16 on the firewall? and vice versa if the device on 36.12.2.3 has a route to reach 36.8.2.3&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 May 2014 03:47:13 GMT</pubDate>
    <dc:creator>nchong</dc:creator>
    <dc:date>2014-05-29T03:47:13Z</dc:date>
    <item>
      <title>Global Protect - ip address for portal web service restricts visitors by their ip address - WHY?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-ip-address-for-portal-web-service-restricts/m-p/16037#M11715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are a bit confused. It appears that our ip address setting under Network&amp;gt;GlobalProtect&amp;gt;Portals must be set to either an IP Range or IP/Subnet, therefore it is not necessarily a single ip address (which is what I thought it should be).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The part that is confusing us, is that the ip address/subnet setting for the portal web service is determining which users (by their ip address) can connect to the vpn web login.&amp;nbsp; If the visitor's ip address does not fall into the same subnet, they are unable to launch the login website (it just times out).&amp;nbsp; It seems that ALL ip addresses should be able to launch the vpn web login screen?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If my portal web service ip address is (36.8.2.3/16) BOTH 36.8.5.12 AND 36.8.5.23 can launch the vpn login website.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If my portal web service ip address is (36.8.2.3/24) 36.8.12.23 can launch the vpn login website, but, 36.12.2.3 can NOT launch the vpn login website?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am confused as to why this TARGET portal web service ip address impacts the visitors based on their ip address?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 May 2014 19:00:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-ip-address-for-portal-web-service-restricts/m-p/16037#M11715</guid>
      <dc:creator>shank</dc:creator>
      <dc:date>2014-05-27T19:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect - ip address for portal web service restricts visitors by their ip address - WHY?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-ip-address-for-portal-web-service-restricts/m-p/16038#M11716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The IP address that you select is actually based on the interface that you have selected. So its actually a single IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From your description that you are able to connect on the same subnet but not on a different subnet tells me that you have a routing issue. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have default route or a static route with 36.12.0.0/16 on the firewall? and vice versa if the device on 36.12.2.3 has a route to reach 36.8.2.3&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 May 2014 03:47:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-ip-address-for-portal-web-service-restricts/m-p/16038#M11716</guid>
      <dc:creator>nchong</dc:creator>
      <dc:date>2014-05-29T03:47:13Z</dc:date>
    </item>
  </channel>
</rss>

