FQDN exclusion Global Protect enforce connection

[Sec101]

Is it possible to FQDN exclude  your local domain *.localdomain  when enforcing network Global Protect connection?   Could this be used as a workaround for not having pre-logon configured?  

How/why is there not a enforce global protect connection only while "outside" of the network?

[MickBall]

Hi, not sure i understand the first part of your post, and  second part (i think) would not be enforced if using internal host detection.

[Sec101]

This would be for updates in the case a user is not signed in/signed out.   Machine would lose connection if no prelogon is setup until user authenticates I think? Mostly regarding updates when a user is not signed into a machine.    But if internal it appears it still enforces sign on for network connectivity even when inside a trusted network.

[MickBall]

do you mean your company domain that is local when at work or any localdomain at that time, only the first option is possible.

are you actually using internal host detection?

[Sec101]

Thank you for the quick reply Mick.   Yes and yes.   If memory serves correct, when not logged in and enforce global protect, computers don't connect to local network I think?

[MickBall]

OK i was not aware of that, I have never used the enforce GP option so cant really advise any further....  also I don't have lab access just now so cant even test.

[Sec101]

I could be missing something, but wish there was an option to not enforce when on local trusted network if internal host detection occurred.   

[MickBall]

sure, I can see what you are asking as GP is not running so how can the local host detection work, it only works when you connect to the portal. if you do manage to apply a local domain then what will happen when outside the office....   will it traverse the VPN or go direct when connected....

[Sec101]

Perhaps the only way to take this is with IP address exclusions then?