The VPN client connects and authenticates against the active Directory correctly, but then is unable to access any IP of the local network (or the local IP of the MX64).
The local network has the range 192.168.1.0 / 24 and the VPN network is in the range 192.168.6.0/24
In the VPN client, I do not observe any route to the 192.168.1.0 network and the packages exit through the gateway to the Internet (logical that they do not arrive).
Solved! Go to Solution.
Good morning @Vincent ,
First question I have to ask, under Security & SD-WAN>Configure>Site-to-site VPN, you should see a list of your local networks attacked to the MX64. On your Client VPN, do you have YES selected under the Use VPN column?
Site to site is Off. The list of LAN attached are seen under Addressing and VLANS. The VPN is client to VPN server.
What os is the client?
If you are using macOS you must ensure you tunnel all traffic through the VPN for it to work correctly. Under advanced as per this screenshot 🙂
Do you have any firewall rules in place?
Probably not as you said the traffic is passing to the gateway, but I want to make sure anyway. The host network the client is in isn't 192.168.1.0/24 too, is it? As that could cause problems when trying to reach devices in that network.
192.168.1.0/24 is probably the most used subnet in the world so sooner or later this would cause issues.
Under Addressing & VLAN I have
Under Client VPN ...
Under Firewall ..
At the client PC once connected ..
I don´t know what IP is 192.0.2.1 and logically as DNS server is of LAN remote don´t resolve any name.
The requisite is check the option at client VPN configuration of Route all traffic over remote network and that remote machines have the gateway the MX.