We have a server running 2016 Standard with Essentials role installed. VPN/Remote access was previously working fine when the server was migrated from SBS 2011 a few months ago. Just set up a new laptop on the network and found that VPN no longer works.
At first users were able to connect but couldn't access any resources. I've tried various fixes, removed anywhere access and reconfigured it but still having issues, infact users can no longer connect and get error stating 'you might need to change the network settings for this connection'.
On the server itself, the event log shows event 20253 Error "RoutingDomainID- {00000000-0000-0000-0000-000000000000}: CoId={4D12FFF1-BD02-0001-115E-134D02BDD701}: The user DOMAIN\administrator connected to port VPN2-1 has been disconnected because no network protocols were successfully negotiated.
If it helps, DHCP is handled by the Router.
Any suggestions on how to fix this would be greatly appreciated.
Thanks
Mike
Update:
I had a vague recollection of having to assign a range of IP addresses for VPN on a server many years ago, had to hunt around for the exact commands to do this as I haven't done it for a long time. Anyway, I ran the powershell comamnd "Set-VpnIPAddressAssignment -IPAssignmentMethod "StaticPool" -IPAddressRange "192.168.1.215", "192.168.1.225" -PassThru", and low and behold I can now connect to the VPN and can also browse shared folders.
As far as I'm aware, this shouldn't actually be necessary even if using a Router for DHCP so would still like to try and work out why the DHCP assignment won't work without statically assigning an IP range. If anyone can shed any light on this I'd appreciate it.