#Globalprotect not connecting windows 10#
#Globalprotect not connecting windows#

What you want openconnect to do when it connects via an internal gateway with connection-type=notunnel is: HmmmвЂ¦ let me make sure I understand here. Is this possible to allow connection-type=notunnel, and keeping the ssl session opened to have a sort of keepalive ? рџ¤·вЂЌв™‚пёЏДЇor my use case, notunnel is expected, as we use globalprotect only as an userid agent, and we don't want to etablish a tunnel because all network resources are already available via routing. I had never seen the possibility of an gateway before, nor had I ever seen connection-type=notunnel, so openconnect doesn't look for these possibilities.

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.

#Globalprotect not connecting 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. I'm having this issue with only 4 users.If it's not the right place to ask this, let me know.

#Globalprotect not connecting windows 10#

I checked the response in version 4.1.12 but no luck.Д«ut some of my other users running windows 10 are able to connect. I tried it but response is same.Д¬urrently firewall is running PAN 9.0.2 and GPC 5.0.2. It is said in article this can be resolved if we reinstall the global protect after deleting the palo alto network folder in program files. When I dig into debug logs, i found below intersting logs. When I'm trying to connect global protect from agent it gives an error 'Could not connect to gateway contact your IT administrator'.