My active routes is not properly updating when using IPSec VPN, what diagnostics am I missing

Ryctas 20 Reputation points
2025-02-26T07:11:29.5933333+00:00

Hello,

I'm running diagnostics on 2 Windows PC, and I'm running out of clues where the issue lies.

Both PCs are using the same Windows 11 Pro 24H2 version, both have the same Network drivers, both are using the same FortiClient version, and I've copied and used the same configuration from both with one another.

I have no problems getting an IP, getting connected, etc. My problems lie with split tunneling.

On one PC, it properly updates its Active Route. It adds the route 10.0.0.0/8 and it's gateway etc

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.114 25

10.0.0.0 255.0.0.0 10.213.134.1 10.213.134.0 1

On the "Broken" PC, it does not update properly, it defaults to 0.0.0.0/0 as if it were Full Tunnel.

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.114 25

0.0.0.0 0.0.0.0 10.213.134.1 10.213.134.0 25

As mentioned, I'd like to blame the software, but I've quadrupled verified settings/versions/etc.

I've attempted Flushdns, Route /f, I tried updating ethernet adapters, verified drivers, nothing new is available. Any clues as to where the issue lies would help.

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2025-03-03T02:13:26.3666667+00:00

    Hello,

    For two devices with the same configuration but different routing table behaviors, the following are the key directions for investigation and solutions:

    Check the priority of the Split Tunneling rules in FortiClient: Some VPN clients may override local routing rules through configuration files or management consoles. Even if the configurations appear the same, the actual effective policies may differ due to permissions or configuration loading order.

    Check the VPN connection logs (the FortiClient log path is usually C:\ProgramData\Fortinet\FortiClient\Logs), focusing on warnings or errors related to failed route injection.

    Check the group policy entries that may affect routing:

    Run gpedit.msc, and expand Computer Configuration → Administrative Templates → Network → Network Connections.

    Confirm that policies such as "Prohibit the use of route-based VPN" or "Force all traffic through VPN" are not enabled.

    Temporarily disable the firewall/antivirus software (such as Windows Defender Real-time Protection, third-party firewalls), and test if the routing table returns to normal.

    Reset the underlying network stack of the system: Perform a comprehensive network stack reset (requires administrator privileges).

    Force delete conflicting routes and observe if the VPN client re-injects the correct routes (note: a VPN connection restart may be required).

    I hope the information above is helpful.

    Best regards

    Zunhui

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.