About goran.katava

Hi, it should be working. You do need license for that.       ... View more

@Mick_Ball    You can use '?' in order to see available commands. When in set config mode try next :   set global-protect global-protect-gateway GATEWAY-NAME remote-user-tunnel-configs ?   Thus for domain exclusion it is:   set global-protect global-protect-gateway GATEWAY-NAME remote-user-tunnel-configs CONFIG-NAME split-tunneling exclude-domains list DOMAIN-ENTRY ... View more

Yea, I am sure, IPSEC mode.    All sudden it started working. It was most probably blocked by ISP.   ... View more

Hi,   Here is what I use for O365 (optimized option):   set global-protect global-protect-gateway GATEWAY-NAME remote-user-tunnel-configs CONFIG-NAME split-tunneling exclude-access-route [ 13.107.18.10/31 13.107.6.152/31 13.107.64.0/18 13.107.128.0/22 13.107.136.0/22 23.103.160.0/20 40.96.0.0/13 40.104.0.0/15 40.108.128.0/17 52.96.0.0/14 52.104.0.0/14 52.112.0.0/14 104.146.128.0/17 131.253.33.215/32 132.245.0.0/16 150.171.32.0/22 150.171.40.0/22 191.234.140.0/22 204.79.197.215/32 ] ... View more

Hi Rajjair, Mickball,   I don't have Global Protect license, and therefor can't use split tunnel based on application/service.  As I mentioned in previous comment, version 9.0.x seems to support destination domain, even with no license.    We use MS Flow as described in next link, in order to get alerted on any changes of IP ranges or domains.   https://techcommunity.microsoft.com/t5/office-365-networking/use-microsoft-flow-to-receive-an-email-for-changes-to-office-365/m-p/240651         ... View more

Hi RJ,   I followed advice from @Mick_Ball, and realized that 'optimized' should be enough for split-tunnel on Global Protect.  Search for category 'optimize' on next : https://endpoints.office.com/endpoints/worldwide?clientrequestid=b10c5ed1-bad1-445f-b386-b919946339a7   It takes 4 domains and about 20 subnets.   set global-protect global-protect-gateway GATEWAY_NAME remote-user-tunnel-configs test-Office365-offloading split-tunneling exclude-access-route [ 13.107.18.10/31 13.107.6.152/31 13.107.64.0/18 13.107.128.0/22 13.107.136.0/22 23.103.160.0/20 40.96.0.0/13 40.104.0.0/15 40.108.128.0/17 52.96.0.0/14 52.104.0.0/14 52.112.0.0/14 104.146.128.0/17 131.253.33.215/32 132.245.0.0/16 150.171.32.0/22 150.171.40.0/22 191.234.140.0/22 204.79.197.215/32 ] set global-protect global-protect-gateway GATEWAY_NAME remote-user-tunnel-configs test-Office365-offloading split-tunneling exclude-domains list outlook.office.com set global-protect global-protect-gateway GATEWAY_NAME remote-user-tunnel-configs test-Office365-offloading split-tunneling exclude-domains list outlook.office365.com set global-protect global-protect-gateway GATEWAY_NAME remote-user-tunnel-configs test-Office365-offloading split-tunneling exclude-domains list company-name.sharepoint.com set global-protect global-protect-gateway GATEWAY_NAME remote-user-tunnel-configs test-Office365-offloading split-tunneling exclude-domains list company-name-my.sharepoint.com     ... View more

Sorry, my bad. The firewall type 820 was running 8.1.11. After upgrade to 9.0.5 it is all working good. No Global Protect license is needed for split-tunnel based on domain. I also notice that included domains are required for Office 365 to function properly. That because we use SSO and Microsoft is expecting to see logins coming from registered public addresses. For that I include domains from option 56 as on next Microsoft page: https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges The rest I add to excluded list. In order to configure I use set cli like in next example:   excl: set global-protect global-protect-gateway GATEWAY_NAME remote-user-tunnel-configs CONFIG_NAME split-tunneling exclude-domains list *.microsoft.com   incl: set global-protect global-protect-gateway GATEWAY_NAME remote-user-tunnel-configs CONFIG_NAME split-tunneling include-domains list login.microsoft.com   From this lists is visible why included list is needed.   On the portal I use option not to use tunnel for all DNS queries. That way the clients use local ISP for resolving Microsoft addresses, in order to connect to the nearest pod.    Let me know if you need complete list of Office 365. I had to tweak it in order to have less than 200 entries. ... View more

I have configured split tunneling on version 9.0.4 in order to offload Office365 from the tunnel. I have added 163 entries in excluded domains. That works fine so far. I don't understand the purpose of included domain list. I even notice that my vpn is not working when I add a list on PA-820. It is working on PA-3200. Which list has a precedence in case of conflicting entries? I can't find this documented on PA. ... View more

How is this solved? Solution is showing that Global Protect VPN doesn't support IPv6. Is that it? ... View more

I notice this old thread, but would like to comment on it and maybe get more replies.  We have hosted Global Protect in China with mixed results. It used to work on Verizon line, but since we switched to China telecom it is not working. It seems like the problem is ssl connection, and that ssl requests are not even reaching the portal/gateway.    ... View more