VPN Connects Successfully but Remote Computers Are Unreachable

The first thing to investigate is overlapping LAN ranges. If a user's home router and the office use the same subnet, the computer will usually try to reach the work device locally instead of sending that traffic through the VPN. The cleanest long-term fix is to renumber the office network to a less common private range, although that can be a major project. Changing the affected home networks may be a practical short-term workaround.

Make sure the VPN address pool and routing are configured separately from both the office LAN and the clients' local networks. A dedicated VPN subnet is still necessary, but it will not fully solve a conflict when the user's local LAN overlaps the destination subnet. Check the client route table while connected and confirm that traffic for the work subnet is being sent through the tunnel.

Since this is a FortiGate and the tunnel is full tunnel, review the firewall policies and run a flow trace while reproducing the problem. A traceroute timing out alone does not identify whether the issue is routing, policy, or return traffic. Also verify the VPN type, source and destination interfaces, firewall rules, and whether the remote computer's own firewall allows traffic from the VPN pool. MTU is worth checking too, but subnet overlap and routing are the stronger suspects.