Is this an expected behavior to ignore internal server or I'm having an issue with my configuration ?
(By the way, since GP support has been merged into the official releases as of v8.00, might want to move this over to at some point…) Thanks for the thorough and useful description. When connecting using openconnect, my internal gateway is not available as a choice of gateway servers available but It is described in the XML file when using -dump.
#Global protect not working windows#
Only issue for us as the moment is our few linux clients are not able to connect to the internal gateway.Ĭonfiguration of mixed external and internal gateway is documented on Palo Alto website.Ĭonnection to internal gateway with official windows client works great client is dynamically choosing the gateway it needs according to a dns request and the client IP. There are others way to populate userid information, but we found this one to be the more accurate. This help us manage internal access per user and groups in the firewalls rules instead of IP. The mean of an internal gateway, is to populate user-id information into the palo alto We use it as an user-id agent deployed on all users computers. When I use openconnect on an external network, I am able to connect, no problem, it works well. GlobalProtect Portal is configured only on the external, and each as a Gateway configured. We use 2 PAN on our network: one for all external access, and one for all internal access. If it's not the right place to ask this, let me know.
0 kommentar(er)
