Setting up a VPN on Windows Server 2012 R2

I'm having some issues getting a VPN to work as expected. I have a 2012R2 server at home. This acts as a public-facing web server, inteal file server, and a few other things. I'm trying to have it function as a VPN server so I can access the SMB shares from elsewhere and so other clients can coect to my LAN over the inteet for network gaming.

I've installed the Remote Access role, and set up a VPN on the server. All seems fine. I can coect to it exteally and authenticate fine. The server status shows that the client is coected. This is where I run into issues. Once coected the client doesn't have access to the inteet nor to the network resources. It appears they are provided with a local IP (from my router's DHCP server) however they are unable to so much as ping any network device.

Ideally I'd like to route the inteet traffic through the VPN- or at least give clients the option to do so. I've been looking around the settings but can't seem to enable the VPN clients access to the LAN or the inteet coection.

There are loads of things online, but people tend to end up split-tueling at the client-side and that doesn't really solve my "no network resources" issue.

Anyone know of any typical issues that occur when setting up a VPN in this sort of way? Anything I've missed? Any help would be greatly appreciated.

Cheers, Dean