03-17-2021 10:30 AM - edited 03-17-2021 10:36 AM
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?
03-17-2021 02:58 PM
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.
03-18-2021 02:46 AM
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?
03-18-2021 06:00 AM
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?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!