The VPN tunnel is established correctly but internal resources remain inaccessible. The problem is usually after the authentication: routing, DNS, policies19 or conflict of address.
Probable causes
- route of the network of the remote or uninstalled network
- missing 1966 politics between VPN and the LAN
- Internal DNS not provided to client
- overlap between the customer’s local network and the company’s network
Verifications.
- Check the VPN address — To take up the IP address, the gateway and the routes obtained after connection.
- Testing an internal IP. — First test an internal IP address known to separate routing problem and DNS problem.
- Control the routing table — Check that a route to the internal sub-network exists on the client side and on the Burden side.
- Test the internal DNS — Solve an internal DQF and compare with the expected answer.
- Checking policies —To ensure that VPN traffic → LAN and return LAN → VPN are allowed.
Commands
route printipconfig /allnslookup server.domaine.localSolutions.
- correcting the routes pushed by the VPN
- add or correct policy
- provide internal DNS to VPN client
- change plan of address if client network overlaps the network
When to climb?
Escalader if the tunnel is established but no flow crosses despite correct roads and policies, or if the problem concerns several sites/tunnels simultaneously.
See also:. VPN connected without access to LAN.