Share this article
Improve this guide
SOLVED: VPN won’t work on Windows Server 2012
6 min. read
Updated onOctober 4, 2023
updated onOctober 4, 2023
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
A VPN can be installed and configured on a WindowsServer 2012by running the Setup Anywhere Access wizard and selecting the VPN option.
When you choose to enable this option using the wizard, roles or features such asRemote Access, DirectAccess and VPN (RAS), IP and Domain Restrictions, IIS Management Scripts and Tools, Network Policy and Access Services Tools, and Windows Internal Databaseare installed on the server.
It is also possible to enable these roles and/or features from the Server Manager or PowerShell command-lets, but it is however recommended to enable it through the wizard itself.
WindowsServer 2012allows client machines to join their server without being in the company network through the Remote Domain Join feature.
So, if VPN is enabled on the server, you canconnect a remote clientto the local network via your VPN, and run the Connect wizard then join the remote client to the server – a simple and straightforward process.
It is important to note, however, that the Server 2012 automatically manages to route for the VPN, so Routing and Remote Access (RRAS) UI is hidden on the server to prevent tampering of these settings.
VPNs are also deployed such that there’s little need for manual configurations on the server or client.
If correct TCP ports are open on the firewall and sent to the server, and the VPN was enabled while running the wizard, the VPN should work instantly, with proper protocols selected.
Users of the WindowsServer 2012have reported concerns when their VPN is not working with server 2012, and this article looks at some of the common issues and their solutions.
World-class 24/7 support with 83% for a 3 years plan and 3 months free.
Amazing connection speed with 35% off and 3 months free for the 1-year plan.
Best security protocols with 83% off and 2 months free for a 2-year plan.
What can I do if VPN won’t work on Windows Server 2012?
1. Error 850
When thiserrordisplays, the message reads:The Extensible Authentication Protocol type required for authentication of the remote access connection is not installed on your computer.
If you set up the VPN connection manually, then you’ll get thiserrorwhen VPN is not working with server 2012.
Thiserrorshows that none of the protocols have been selected in the VPN connection properties, so to fix this, you need to selectAllow these protocolson theSecurity tabof the VPN connection.
Microsoft CHAP Version 2 (MS-CHAP v2) would be automatically selected if you click this option, then clickOKto apply the changes.
If you get Internet or network resource access issues, you could be using the default gateway of the remote network. Use the steps detailed above to fix this in no time.
2. Error 800
Note:If this is a different certificate, change the certificate to match the one on the IIS. Otherwise, you may use this command to modify the thumbprint of this certificate for the Secure Socket Tunneling Protocol (SSTP) Service:
Thiserrordisplays asThe remote connection was not made because the attemptedVPN tunnels failed.
When this happens, theVPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.
This connection failure could be because either 443 isn’t allowed on the firewall or there’s a certificate mismatch in the RRAS and IIS (default website).
To resolve this issue, pay attention to the guidelines above.
Once you ensure that the certificate on the Default Web Site and SSTP are the same, the problem should go away.
3. Error 720
Note:On certain occasions, it has been noted that the on-premise client would show connected to the hosted Windows Server 2012 R2 Essentials.
However there may not be any connectivity between the VPN client and the Server Essentials.
In such scenarios, check the events forRemoteAccess-MgmtClientandRemoteAccess-RemoteAccessServeron the Event Viewer.
This error displays asA connection to the remote computer could not be established. You might need to change the network settings for this connection.
If a VPN client is unable to obtain an IP address from the VPN server, then you may get Error 720 when the VPN is not working with server 2012.
In Server Essentials, usually, the DHCP is hosted on a different device.
Did any of these solutions help with the VPN not working server 2012 issue on your computer? Let us know by leaving a comment in the section below.
When this doesn’t happen, VPNs can be installed and configured. That’s what you can clearly do on Windows Server 2012.
Yes, it’s still supported. The end-of-extended support date for Windows Server 2012 r2 is Oct. 10, 2023.
[wl_navigator]
Milan Stanojevic
Windows Toubleshooting Expert
Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he spends most of his time learning about computers and technology.
Before joining WindowsReport, he worked as a front-end web developer. Now, he’s one of the Troubleshooting experts in our worldwide team, specializing in Windows errors & software issues.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Milan Stanojevic
Windows Toubleshooting Expert
Before joining WindowsReport, he worked as a front-end web developer. Now, he’s specialized in Windows errors & software issues.
