First install the “Remote Access” via Server Manager or Windows PowerShell.
Select the “DirectAccess and VPN (RAS)” role services.
On the next steps just use the default settings.
After that you can have a look at the Overview screen and install the role.
After the features are installed, which can take a while to finish you see the link for the Getting Started Wizard. Click on “Open the Getting Started Wizard“. This opens the Routing and Remote Access MMC
Right click on the Server name and click on “Configure and Enable Routing and Remote Access“.
On the new wizard select “Custom configuration“.
Select “VPN Access“.
After you have click finish you can now start the Routing and Remote Access service.
If you have an other firewall between the internet and your Windows Server you have to open the following Firewall port sand forward them to your Windows Server:
For PPTP: 1723 TCP and Protocol 47 GRE (also known as PPTP Pass-through)
For L2TP over IPSEC: 1701 TCP and 500 UDP
For SSTP: 443 TCP
After the installation Users have to be enabled for Remote Access to connect to your VPN Server. On a standalone server this can be done in the Computer Management MMC, in a domain environment this can be done in the user properties of an Active Directory user.
If you don’t have a DHCP Server in your environment you have to add a static IP address pool. This is often needed if you have a single server hosted at a service provider. In the properties of your VPN server you can click on the IPv4 tab and enable and configure the “Static address pool”.
Event ID 20271: The account does not have permission to dial in
Event ID 20258: user connected on port VPN3-127 does not have Remote Access privilege
Cause and Resolution: when we opened Network Policy Server (NPS) from the Administrative Tools, we found the Connections to Microsoft Routing and Remote Access server was set "Deny Access" as shown below.
To fix it, double clicked on the "Connections to Microsoft Routing and Remote Access server" and check "Grant access".