- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
06-19-2024 05:15 AM
How do I ensure that when global protect identifies that it is on the internal network, it does not connect?
06-20-2024 07:48 AM - edited 06-20-2024 07:50 AM
Hello @cylusaragao
If you take a look at the GlobalProtect Panel, you will see the following if you are internal to the corporate network.
06-20-2024 11:33 AM
I want it to not connect to the internal network
06-20-2024 11:52 AM
What is the behavior you intend GP to do when the user is internal to the network? Connect to globalprotect on an external gateway (prisma access or on-prem gateway) or to the internal corporate network?
06-20-2024 01:02 PM
I hope it identifies it is on the internal network and does not connect
06-24-2024 10:23 AM
In order to achieve this. You have to configure internal host detection as specified in the link below. You only need to configure the IP address and the hostname under internal host detection in order to serve the purpose of not connecting to globalprotect when internal to the network.
When the user attempts to log in, the app does a reverse DNS lookup of an internal host using the specified IP Address to the specified Hostname.
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!