How to fix no LAN access in windows server 2016 vpn?

Question

VPN

Hello to all dear Khabarovsk residents, the following embarrassment occurred with VPN:
What we have:
Virtual windows server 2016 (latest updates) configured under vpn called gw, it has 2 interfaces (WAN (direct access), LAN) all this on ipv4
The role of RRas is raised in a standard (of which there are many on Google) way and configured via presharedkey with a pool of addresses through which it must enter the local network to access its resources

What happened:
When authenticating on the server, the user receives the correct address, but he does not have access to resources, tracing goes immediately to the path of least resistance (tobish does not even try to go to the vpn address)

How to fix this and what other data you may need to solve what I could not come to in a week after climbing all the circles of Google hell Have

a nice day everyone and thank you for your attention!

Answer 1

The first thing that comes to mind is to check the routing, that the addresses issued by the VPN have the right to go where you want them to go.
The second thing that comes, see how you set up the firewall, didn’t check the box, didn’t specify ports, didn’t give access to the vpn service, etc.
Show at least a tracer to the destination, where the plug is.