Windows 10 won’t connect to RRAS VPN

encryptionnpsrrasvpnwindows-server-2012-r2

Studying MCSA, currently working on a Server 2012 R2 server lab I have set up on a custom built computer.

Current configuration, I have a host computer that is just that, a host, with RRAS installed for internal network (which I call my virtual office) to be able to reach the internet.

In my VIRTUAL OFFICE (via Hyper-V):

I have a DC server set up with Active Directory, DNS and DHCP and a few client computers (mix of Win 7 and 8), all connected with internal switch. I also have an NPS server with two network connections, one to the internal network and an external connection straight to my home router that connects to the ISP.

It took me hours as this is my first time, but I was able to successfully set up a PPTP VPN connection and test it with my physical laptop connected through my cellphone's mobile hot-spot. Configurations are through RRAS and NPS.

I then deleted my nps/vpn server and deleted the vpn connection on my laptop to set everything up again for experience. Then the problems started. I can get authenticated to the RRAS and I can see my connection in the RRAS console, but on the laptop it gets stuck on "creating a connection" for 10-15 and then disconnects. Event viewer on server gives me an error about encryption. I've restarted back to scratch (delete and reinstall server) several times and I always get stuck at this point. I've gone as far as taking 30 minutes to slowly go through every setting on both the laptop and server to make sure it matches. I've even removed any form of encryption for unsecured connection and still failed.

I am lost here. Any ideas? I can't remember the error code in event viewer, will get that tomorrow

Best Answer

As you already stated, you have to make sure that protocol settings, encryption, and authentication settings all match.

When you are sure everything is alright, there is one more thing I had quite often in Microsoft RRAS configurations: The RRAS server will ask Active Directory about the authentication and sometimes, Windows "thinks" it is not on a domain network anymore (check network and sharing center about the network profile). Most of the times it is a DNS problem you have to fix, but I also had cases where I did not see anything wrong and disabling/re-enabling the internal network adapter of the RRAS server solved the problem.

If it is due to incompatible encyrption settings check the correct server (RRAS server if you do not use NPS, NPS server if you do use NPS) policies. Always go for highest encryption standard possible.

Also check that your firewall you might have in between does not block your VPN protocol(s).

Related Topic