https://live.paloaltonetworks.com/t5/general-topics/connecting-to-vpn-windows-network-profile-changes-to-quot-domain/m-p/244764#M69821 <P>It seems that this is caused by the optimized split tunneling feature (domain,&nbsp;<A href="https://docs.paloaltonetworks.com/globalprotect/4-1/globalprotect-app-new-features/new-features-released-in-gp-agent-4_1/split-tunnel-for-public-applications.html" target="_blank">https://docs.paloaltonetworks.com/globalprotect/4-1/globalprotect-app-new-features/new-features-released-in-gp-agent-4_1/split-tunnel-for-public-applications.html</A>) when the configuration includes the AD-domain (eg. *.domain.ltd) to be routed over the VPN tunnel.</P> Thu, 03 Jan 2019 01:08:47 GMT tigeli 2019-01-03T01:08:47Z https://live.paloaltonetworks.com/t5/general-topics/connecting-to-vpn-windows-network-profile-changes-to-quot-domain/m-p/244755#M69820 <P>Just noticed that with Globalprotect 4.1.x the network profile changes to from "Public" or "Private" to "Domain network" for physical network adapter and not just for the VPN adapter while being connected to GlobalProtect service. Also when the VPN session&nbsp;is disconnected the physical adapter profile does not change but instead stays as "Domain network"-profile. On 4.0.x this does not happen.</P><P>&nbsp;</P><P>This is clearly a security issue as one can have different firewall rules for Public/Private/Domain network profiles and having "Domain network"-profile being assigned to network adapter connected directly to Internet is not something I would want. I did not found any documentation for such a behavioural change in the documentation. Anyone else having this issue?</P><P>&nbsp;</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GP 4.0.8" style="width: 309px;"><img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/18137iCE6498F3C39436D4/image-dimensions/309x331/is-moderation-mode/true?v=v2" width="309" height="331" role="button" title="NLA-4.0.8.jpg" alt="GP 4.0.8" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">GP 4.0.8</span></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GP 4.1.8" style="width: 300px;"><img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/18138iC6BEC3943C90783E/image-dimensions/300x317/is-moderation-mode/true?v=v2" width="300" height="317" role="button" title="NLA-4.1.8.jpg" alt="GP 4.1.8" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">GP 4.1.8</span></span></P><P>&nbsp;</P><P>&nbsp;</P> Wed, 02 Jan 2019 23:54:49 GMT https://live.paloaltonetworks.com/t5/general-topics/connecting-to-vpn-windows-network-profile-changes-to-quot-domain/m-p/244755#M69820 tigeli 2019-01-02T23:54:49Z https://live.paloaltonetworks.com/t5/general-topics/connecting-to-vpn-windows-network-profile-changes-to-quot-domain/m-p/244764#M69821 <P>It seems that this is caused by the optimized split tunneling feature (domain,&nbsp;<A href="https://docs.paloaltonetworks.com/globalprotect/4-1/globalprotect-app-new-features/new-features-released-in-gp-agent-4_1/split-tunnel-for-public-applications.html" target="_blank">https://docs.paloaltonetworks.com/globalprotect/4-1/globalprotect-app-new-features/new-features-released-in-gp-agent-4_1/split-tunnel-for-public-applications.html</A>) when the configuration includes the AD-domain (eg. *.domain.ltd) to be routed over the VPN tunnel.</P> Thu, 03 Jan 2019 01:08:47 GMT https://live.paloaltonetworks.com/t5/general-topics/connecting-to-vpn-windows-network-profile-changes-to-quot-domain/m-p/244764#M69821 tigeli 2019-01-03T01:08:47Z