https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-split-dns-tunnel-windows-firewall-profile/m-p/592628#M5585 <P>Does anybody see the same behaviour with GlobalProtect in a Split DNS/Tunnel scenario?</P> <P>&nbsp;</P> <P>Include Domains: *.company.tld&nbsp; (internal DNS name space used in Active Directory)</P> <P>&nbsp;</P> <P>When GlobalProtect is disconnected, Windows Firewall profile for physical network adapter is public.</P> <P>But when GlobalProtect tunnel is connected, then the physical network adapter switches to domain profile and therefore exposes open ports to internet on the client (e.g. when client has a public reachable IP address on physical network adapter).</P> <P>Only the virtual GP network adapter should switch to domain profile, physical adapter should stay in public profile.</P> <P>&nbsp;</P> <P>&nbsp;</P> Mon, 22 Jul 2024 11:03:20 GMT Anon1 2024-07-22T11:03:20Z https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-split-dns-tunnel-windows-firewall-profile/m-p/592628#M5585 <P>Does anybody see the same behaviour with GlobalProtect in a Split DNS/Tunnel scenario?</P> <P>&nbsp;</P> <P>Include Domains: *.company.tld&nbsp; (internal DNS name space used in Active Directory)</P> <P>&nbsp;</P> <P>When GlobalProtect is disconnected, Windows Firewall profile for physical network adapter is public.</P> <P>But when GlobalProtect tunnel is connected, then the physical network adapter switches to domain profile and therefore exposes open ports to internet on the client (e.g. when client has a public reachable IP address on physical network adapter).</P> <P>Only the virtual GP network adapter should switch to domain profile, physical adapter should stay in public profile.</P> <P>&nbsp;</P> <P>&nbsp;</P> Mon, 22 Jul 2024 11:03:20 GMT https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-split-dns-tunnel-windows-firewall-profile/m-p/592628#M5585 Anon1 2024-07-22T11:03:20Z