In Windows 7 you an create VPN connections for PPTP, L2TP or SSTP. To delete a connection you can not just right click and press delete. But it’s still very simple, but a lot of people can’t find where you can remove VPN connections, because it is a kind of hidden ;-).
This is a modified document which I wrote for a Microsoft Workshop at KTSI. It’s a Desgin, Step by Step and a Troubleshooting Guide for Microsoft DirectAccess. This is made for SMB or LAB environments not for Enterprise Deployments.
I hope this guide can help you deploy DirectAccess in your environment and you can enjoy DirectAccess like I do ;-)
In the last 3 weeks we had do some little Windows Server projects in a Microsoft Workshop at KTSI. Since I was really interessted in Microsoft DirectAccess as an alternative to “legacy” VPN such as PPTP or L2TP, I made a little project out of that and installed DirectAccess in my LAB. And I also created a documentation step by step documentation for LAB and SMB installations of DirectAccess.
I had some respect of the installation of DirectAccess and the requirements of DirectAccess. But to my surprise after the first try everything worked fine. So if you do everything step by step and pay attention to the details you will succeed.
Now to DirectAccess, it’s not just another VPN technology. It can save users and the IT deparments a lot of time. How many hours do you have spent do troubleshoot VPN connection problems? Now with DirectAccess users can work with their notebooks as they were within the company network. You don’t really care about firewalls or connection losses.
But more on DirectAccess later, I will post the step by step guide later this week.
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.
- Install the Role “Network Policy and Access Services” with the Server Manager
- Select the Role Services “Routing and Remote Access Services”
- Configure and Enable Routing and Remote Access in the Server Manager.
- Choose “Custom Configuration” if you just have one Network Interface in the Server
- Choose “VPN access”
- Finish and click next
- Allow access for users “Network Access Permission”. You can set that in de Dial-In Tab under the User Premission.
- 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.
- Right click on “Routing and Remote Access” and open Properties
- Click on the IPv4 Tab and check “Static address pool”
- Add a static address pool of private IP addresses
- 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:
My name is Thomas Maurer. I am a Senior Cloud Advocate at Microsoft. I am part of the Azure engineering team (Cloud + AI) and engage with the community and customers around the world. I am located in Switzerland. I am focusing on Microsoft technologies, especially cloud and datacenter solutions based on Microsoft Azure, Azure Stack and Windows Server. Opinions are my own.