Lỗi 812 vpn windows server 2008 r2 ras vpn năm 2024

This HowTo should show you how to install a VPN Server on Windows Server 2008 R2. This is a HowTo for a small environment or a stand-alone hosted Server.

1. Install the Role “Network Policy and Access Services” with the Server Manager
2. Select the Role Services “Routing and Remote Access Services”
3. Configure and Enable Routing and Remote Access in the Server Manager.
4. Choose “Custom Configuration” if you just have one Network Interface in the Server
5. Choose “VPN access”
6. Finish and click next
7. Allow access for users “Network Access Permission”. You can set that in de Dial-In Tab under the User Premission.
8. Open Ports in your FirewallFor PPTP: 1723 TCP 47 GRE For L2TP over IPSEC: 1701 TCP 500 UDP For SSTP: 443 TCP

Optional: If you don’t have a DHCP Server in your local network you have to add a static address pool. This could be if you have a stand-alone Server by your provider.

1. Right click on “Routing and Remote Access” and open Properties
2. Click on the IPv4 Tab and check “Static address pool”
3. Add a static address pool of private IP addresses
4. Add secondary IP Address to the Server network interface which is in the same subnet as this pool.

I also have other posts for about installing VPN on Windows Server:

• How to Install VPN on Windows Server 2012
• How to Install VPN on Windows Server 2012 R2
• How to Install VPN on Windows Server 2016
• How to Install VPN on Windows Server 2019

Tags: Access Services, L2TP, Microsoft, network Policy, Network Policy and Access Services, Ports, PPTP, Remote Access, role, routing, routing and remote access services, SSTP, static address pool, Virtual Private Network, VPN, VPN Windows Server 2008 R2, Windows, Windows Server, Windows Server 2008 R2 Last modified: April 25, 2019

About the Author / Thomas Maurer

Thomas works as a Principal Program Manager & Chief Evangelist Azure Hybrid at Microsoft (Cloud + AI). He engages with the community and customers around the world to share his knowledge and collect feedback to improve the Azure hybrid cloud and edge platform. Prior to joining the Azure engineering team (Cloud + AI), Thomas was a Lead Architect and Microsoft MVP, to help architect, implement and promote Microsoft cloud technology. If you want to know more about Thomas, check out his blog: www.thomasmaurer.ch and Twitter: www.twitter.com/thomasmaurer

Not sure what this was about. Just moved the PPTP VPN server on a client network from their old Windows 2003 Server to Windows Server 2008 and suddenly remote clients were getting the error:

Error 812: 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.

Blah! Nothing changed, just targeting a new server. Found the answer in the NAS policy and it was stupid. For some reason, the default is to deny connections from the Microsoft VPN client.

To fix:

1. Open the routing and remote access management console.
2. Right-click on “Remote Access Logging and Policies” then click on Launch NPS.
3. Click on “Network Policies” in the left pane
4. Right click on the “Connections to Microsoft Routing and Remote Access server” policy in the right pane and select properties.
5. Change from “Deny Access” to “Grant Access” on the radio buttons in the middle.
6. Hit Apply

Not sure why this is denied by default. Don’t really care, it works when you allow it. Hope this helps someone else!

Now, that you’ve got the vpn working, why not write a 4 line batch file to automate the connection and drive mapping for your users?