Windows client vs macOS

mieslep

Apologies in advance if this is in the wrong spot.

I'm switching from macOS to Windows 10 (long saga, but the net of it is the new MBP is not worth the money).

Am having problems with what I believe to be default routes when connected to VPN; to the same gateway on my Mac, network traffic seems to route to my local gateway in preference to the VPN gateway, whereas on Windows it seems the reverse. Network latencies appear quite slow in comparison (the new Windows machine is much higher-spec btw).

Suspecting a routing problem:

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.202.1   192.168.202.21     25
<100+ lines of IP-specific routes I have received from the server omitted...don't ask...>
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link      172.16.23.34    262
  255.255.255.255  255.255.255.255         On-link    192.168.202.21    281

I am guessing Windows is using "Metric" somehow to determine precedence.

Is there a way, on the client side, I can change this?

TinCanTech

mieslep wrote <100+ lines of IP-specific routes I have received from the server omitted...don't ask...>

this is your problem .. you should probably ask the server admin.

Or you might try this:
HOWTO: Request Help !

mieslep

Not sure why this is the problem? It is the same list of specific IP addresses that macOS had to deal with. I'm not saying that my guess is right, mind you...just that simple things like DNS lookup which are near-instant on macOS are taking 1-2 seconds on Windows, but only when on the VPN.

mieslep

Okay, Wireshark tells me that DNS is not resolving on the VPN interface, so that's not the problem. I think I've tracked it down to using Cloudflare DNS (1.1.1.1 / 1.0.0.1) on my LAN interface, this VPN, and Windows...seemingly a combination of the three is leading to DNS resolving problems. (The VPN interface uses Google DNS, fwiw.) Switching to either my ISP or Google DNS and the problem seems to have resolved.