Error in point to site VPN "The connection was prevented because of a policy configured on your RAS/VPN server."

Question

_{Tuesday, August 14, 2018 11:08 AM | 1 vote}

I have a vm in azure from where i connect to different vm in my azure subscription using point to site connection.
i have vnet gateways for all those vms.

suddenly my one vpn connection stopped and giving error like :

"The connection was prevented because of a policy configured on your RAS/VPN server. 
Specifically, the authentication method used by the server to verify your username and password may not match the authentication method 
configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error. (Error 812)"

i could connect to other vnet gateways and vms. but could not connect some vms under one vne and gateway, i am getting above message for them.
All vms are 2012R2.

please help

All replies (8)

_{Tuesday, August 14, 2018 9:48 PM ✅Answered | 2 votes}

I found the solution as I'm having the same issue. We are not using RADIUS, so that is a useless alley to venture down for a solution.

I found this other Social post which lead me to the real answer: https://social.msdn.microsoft.com/Forums/en-US/ec17e567-ffc2-4aa1-8b04-7e1249d403c1/vpn-azure-not-connected-with-windows-7?forum=WAVirtualMachinesVirtualNetwork

It will lead you to this link: /en-us/azure/vpn-gateway/point-to-site-about#tls1

The answer for me was to install those two updates listed there, and run these commands: 

reg add HKLM\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\13 /v TlsVersion /t REG_DWORD /d 0xfc0reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp" /v DefaultSecureProtocols /t REG_DWORD /d 0xaa0if %PROCESSOR_ARCHITECTURE% EQU AMD64 reg add "HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp" /v DefaultSecureProtocols /t REG_DWORD /d 0xaa0

After a reboot, the VPN began working again.

_{Tuesday, August 14, 2018 2:44 PM | 1 vote}

This error occurs if the RADIUS server that you used for authenticating VPN client has incorrect settings, or Azure Gateway can't reach the Radius server. make sure that RADIUS server is configured correctly.

More information, see Integrate RADIUS authentication with Azure Multi-Factor Authentication Server.

Reference: Troubleshooting: Azure point-to-site connection problems<o:p></o:p>

If this answer was helpful, click “Mark as Answer” or “Up-Vote”. To provide additional feedback on your forum experience, click here

_{Tuesday, August 14, 2018 9:42 PM}

We also started getting this error recently. 

It looks like it started happening right after Microsoft started forcing TLS 1.2. We are not running a Radius server as we are using Certificates for authentication. 

We've done the workaround to Enable TLS1.2 and also reset the VPN Gateway and re-installed the clients but now getting the above error message. 

_{Thursday, September 6, 2018 10:49 AM}

Hi, 

  I am using windows 10 . But still I am getting the error 

"The connection was prevented because of a policy configured on your RAS/VPN server. 
Specifically, the authentication method used by the server to verify your username and password may not match the authentication method 
configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error. (Error 812)"

I tried to use the commands above , but no effect.  

_{Thursday, September 6, 2018 5:40 PM}

@sharonswaroop, just checking if you are using Radius server for authenticating VPN clients.

_{Friday, September 7, 2018 6:40 AM}

Hi,

   I am not using Radius server for authenticating VPN Cleints. 

I use Certficates  for authentication. Also the clients are windows 10 , and server in azure cloud which we try to access via vpn is windows 2016.

_{Sunday, September 9, 2018 4:59 PM}

@sharonswaroop, I will suggest you generate and install a new client certificate for your PS2 connection and see if it helps, feel free to reply for further assistance.

_{Friday, November 23, 2018 5:01 PM}

Hi we are getting the same error. using win 2012 R2. I worked fine earlier. I generated new root and client cert. downloaded and installed VPN client (removed the original).  also unchecked for IKE in the azure portal.  Would we need to update these?   They seem to be for Win 7 client. 

reg add HKLM\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\13 /v TlsVersion /t REG_DWORD /d 0xfc0reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp" /v DefaultSecureProtocols /t REG_DWORD /d 0xaa0if %PROC