VPN Error 812
While it is not usual to come across VPN Error 812 , there is a simple way to get it resolved so don’t be alarmed if you experience it. When you get Error 812, you will see a message telling you the following: The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method configured in your connection profile. Please content the Administrator of the RAS server and notify them of this error”.
Due to the message and the fact that it is not a common error, many VPN users get worried when facing error 812. The error prevents you from reestablishing a connection to the VPN, after it has been disconnected. The good news is that it can be fixed easily and within a few steps. As the message indicated, the error is related to the RSA/VPN server. It is possible to resolve the problem by restarting the RRAS serve. Alternatively, you can allow about one hour and reconnect your VPN.
The main culprit behind this error is Microsoft’s RRAS server. It is possible that the server fails to start every time a VPN connection is initiated, or there is an incorrect configuration that interferes with the running of the server. Here are some of the specific scenarios that could lead to error 812:
- Incorrect authentication protocol.If your VPN client is installed on Windows Vista or later and the authentication protocol of the VPN server is set to MS-CHAP, then you’ll most likely encounter this error. This is because MS-CHAP is no longer being used in later versions of the Windows OS.
- NPS automatically selects the authentication protocol.If your Network Policy Server (NPS) is enabled, it automatically selects what authentication protocol will be used by the server. It is possible that the protocol selected by NPS is in conflict with the VPN authentication protocol, hence causing this error.
- Inconsistent RRAS VPN server configuration. Error 812 occurs when your RRAS settings do not match those on your VPN client system.
Method 1: Set up the External DNS
You’ll very quickly get past the error, if you are willing to access your VPN settings.
1) Type in ncpa.cpl into the Windows search box and press Enter.
2) You will see the network connections. Right click on the VPN connection that you are using and click on Properties.
3) Change the Primary DNS to Domain Controller.
2) Set up the External DNS by accessing the Secondary DNS.
3) Modify the range of the Primary DNS to 18.104.22.168. Save the settings, then restart your VPN.
The VPN Connection Error 812 should go away now. However, if you are still coming across it, you are advised to contact your VPN service provider. As mentioned before, the issue is on the server side.
Method 2: Check the Tunnel Type Settings
If the first solution does not work for you, you can try the following steps:
1) Select additional value to “Tunnel type” Condition, like “L2TP” to obtain value “L2TP OR PPTP”
2) Click Apply, then close the Network Policy.
3) Try connecting the VPN client.
4) Revert the Network Policy to the good value for “Tunnel type” Condition, here it is “PPTP” only.
5) Apply and close the Network Policy.
6) Connect your VPN client. The steps should have set your Network Policy, ensuring that the VPN client functions properly.
Method 3: Contact your Network Administrator
It is possible that Error 812 is showing up because you don’t have enough access rights.
If this is the case, the best solution would be to contact your network administrator. Ask them to update your permissions. You have to make sure that all protocol and network authentication permissions are accurate.
Method 4: Contacting your VPN Provider
In case the previous solution still does not fix the problem, you should try contacting your VPN service provider. They most likely understand the issue and have a handy solution for it.