My organization switched to FortiClient VPN recently, and it does not function correctly through my home GL-MT6000 router.
FortiClient injects a primary DNS on my work laptop in the 100.64.0.0 IP subnet, and all DNS traffic from the laptop fails.
The FortiClient VPN works correctly via a mobile hotspot. I have had no trouble with other VPNs traversing the router.
These are some of the troublshooting steps I have attempted:
- set firewall rules to allow all traffic to and from this device at the top of the rule list.
- installed MiniUPnP and set it to allow UPnP requests only from this device.
- started with Admin Panel version 4.7.7, then upgraded to 4.8.2.
None of these have had any impact on the FortiClient DNS issue.
Hi
Could you please provide us with some more details so we can further check?
- Does FortiClient connect successfully or not?
- After connecting, please run the following commands on your Windows(?) laptop and share the results:
ipconfig
route print
- Please also ensure no other VPN or proxy software is running at the same time, including Tailscale or ZeroTier.
Please disregard. I connected the laptop directly to the modem and the issue persists. This is an ISP issue.
Thank you for swift response and your attention to this matter!
1 Like
This appears to be caused by Windows/FortiClient not correctly setting the routing metric.
# GL-MT6000 - FortiClient connected
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.173 25
0.0.0.0 0.0.0.0 10.247.144.143 10.247.144.142 26
# hotspot - FortiClient connected
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 redacted (hotspot) redacted (hotspot) 35
0.0.0.0 0.0.0.0 10.247.112.130 10.247.112.129 26
Please try manually increasing the metric for Ethernet adapter Ethernet 2 by:
https://www.tenforums.com/tutorials/92180-change-network-adapter-connection-priorities-windows-10-a.html
1 Like
@will.qiu You were absolutely correct. Thank you so much!
We decreased the metric for the 10.x.x.x gateway (Interface index 20 on my laptop) with the following PowerShell command run as administrator:
```powershell
Set-NetIPInterface -InterfaceIndex 20 -AutomaticMetric Disabled -InterfaceMetric 2
```
Now DNS and everything else routes properly. No router issue, no ISP issue, simple configuration of the VPN interface.