FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
This article describes the case when the Windows Firewall is not switching to Domain after a VPN connection, blocking traffic.
Scope
FortiClient.
Solution
There is a lag for the FortiClient to install routes on the endpoint routing table. Sometimes, that lag is significant enough to cause Domain misidentification.
The Windows registry can be edited to disable 'Domain Discovery negative cache' and 'DNS negative cache', to improve the Network Location Awareness (NLA) service when it does the domain detection.
Registry script (Save this script to VPN.reg and run it):
