Twitterfox949

1. Windows Sstp Client Windows 7
2. Windows Sstp Client Mac
3. Windows Sstp Client Download
4. Windows Sstp Client Software

In this guide I will show you how to connect your Windows (all versions) PC/laptop to any VPN service that’s using the SSTP protocol. Secure Socket Tunneling Protocol is very secure and stable but only works on Windows computers. It can avoid firewalls because it runs over port 443 (SSL) which is rarely blocked because it’s used by all web browsers for secure browsing.

Feb 23, 2015 Hi, VPN Error: 0x80420100 indicates that no user certificates on the computer. For VPN server, computer certificate is required in order for SSTP based connection. For VPN client, a certificate is required inside the trusted root CA machine store. SSTP Remote Access Step-by-Step Guide: Deployment. Secure Socket Tunneling Protocol (SSTP): Secure Socket Tunneling Protocol (SSTP) is a tunneling protocol developed by Microsoft. SSTP uses a TCP connection (port 443) for tunnel management. SSTP provides a mechanism to encapsulate PPP traffic over the SSL channel of the HTTPS protocol.

Before we start the connection setup process, you will need to find out the following details (best have them written or printed). If you are connecting to a paid VPN service, just login and your details and settings will be there. If you are connecting via a workplace, please contact your Network Administrator and ask them for the following details:

Required Info

• Your VPN username
• Your VPN password
• The server name or IP address (ie. contoso.com or 102.562.243.12)
• Optional or required encryption
• The password protocol (PAP, CHAP, MSCHAP or EAP)

Windows Sstp Client Windows 7

Once you have this info you can then watch the video above or follow the text guide below.

Connect via SSTP to VPN on Windows (all versions)

1. Click on the Start icon bottom-left of your screen
2. Inside the search box, type Control Panel, then click on the first result
3. Click on Network and Internet, then click Network and Sharing Center
4. Now click on Set up a new connection or network link
5. In the window that opens, select Connect to a workplace, then click Next
6. Click on Use my Internet connection (VPN)
7. Enter the server name or IP address into the Internet address box
8. Enter a unique name you will recognize, ie Contoso (Work) or HomeVPN
9. Leave the Use smart card check box unchecked
10. (Windows 8.1 & 10) Leave Remember my credentials checked
11. Leave Allow other people to use this connection unchecked (unless you trust everyone using the computer)
12. (Windows VISTA, 7) Check the Don’t connect now checkbox
13. Now click on Create (the window will now close)
14. On the left pane, click on Change adapter settings
15. Look for your new connection, then right-click on it, and choose Properties
16. In the Properties window, select the Security tab
17. For Type of VPN select Secure Socket Tunneling Protocol (SSTP)
18. For Data encryption, select the encryption level your VPN service provider requires, if you’re unsure, select Require Encryption first, if you still cannot connect try Optional Encryption
19. For Authentication, select the method your VPN service provider requires, if you’re unsure, select Allow these protocols option, then check PAP, CHAP and MS-CHAP v2 checkboxes
20. Finally click OK to close the Properties window
21. For extra convenience, Right-click on your connection icon again and choose Create shortcut, choose Yes to the alert box. This will create a handy icon on your desktop.
22. Now simply right-click on the connection icon and choose Connect/Disconnect
23. Windows will tell you if the connection was successful
24. If you have any errors or the connection was unsuccessful, double-check all settings or contact your VPN service provider or network administrator.
25. All done!
26. NOTE* If you keep getting Error: 0x800B0109 see this guide

KB ID 0000819

Problem

SSTP gives you the ability to connect to your corporate network from any location that has an internet connection, and is not filtering https. This port is usually open for normal secure web traffic. Traditional VPN connections require ports and protocols to be open for them to work, which makes a solution that runs over TCP port 443 attractive.

Thoughts: While I can see why this is a good idea, Microsoft has basically changed some existing protocols so they work on a port that wont be blocked by most firewalls. This is not a new approach, (Microsoft did it before with RPC over HTTP). I can’t help feeling that the more traffic we push over ports 80 and 443, sooner or later security/firewall vendors are going to statefully inspect/block traffic that isn’t supposed to be on that port. (If you think ‘that would never happen!’ Try running an Exchange Server through a Cisco firewall with SMTP inspection turned on). Anyway, it’s there, I’ve been asked to do a walkthrough, so read on,

Solution

I’ve got a Windows 2012 Server already setup, it’s a domain controller, and is running DNS. You don’t have to have the same server running SSTP/RRAS but in this lab environment that’s what I’m doing. In addition my remote VPN clients will get an IP address from my normal corporate LAN.

1. On the server I have two network cards installed, the first (NIC1) is the normal network connection for the server, the second (NIC2) will be the one that the remote clients get connected to (once they have authenticated to NIC1).

2. Make sure the Internet facing NIC has good comms, and works OK.

3. NIC2 as you can see, does not even need a default gateway.

Windows Server 2012 Add Certificate Services

I’m going to use a ‘self signed’ certificate, if you have purchased one, then skip this section.

4. From Server Manager (ServerManager.exe) > Add Roles and Features > Next > Next > Next > Select > Active Directory Certificate Services.

5. Add Features > Next > Next > Next > Tick ‘Certificate Authority Web Enrolment’.

6. Add Features > Next > Next > Next > Install > Close > From the warning (top right) > Configure Active Directory Certificate Services on this server.

7. Next.

8. Select both Certificate Authority and Certificate Authority Web Enrolment > Next.

9. Next > Next > Next > Next > Next > Next > Next > Configure > Close > Close Server Manager.

10. Open a Microsoft Management Console.

11. File > Add Remove Snap-in > Certificate Authority > Add > Local computer > Finish > OK.

12. Drill down to Certificate Templates > Manage.

Windows Sstp Client Mac

13. From the list that appears locate IPsec > Right Click > Duplicate Template.</p:

14. General tab > Change the name to SSTP-VPN.

15. Request Handling tab > Tick ‘Allow private key to be exported’.

16. Subject Name tab > Tick ‘Supply the request’ > Click OK when prompted.

17. Extensions Tab > Select the Application Policies entry > Edit.

18. Add > Locate the ‘Server Authentication’ policy > OK > OK > Apply > OK > Close the Certificate Template console.

19. From the Certificate templates Folder > New > Certificate Template Issue.

20. Locate the SSTP-VPN entry > OK > Close the MMC.

SSTP Firewall Setup

In this example my server is behind a corporate firewall. If yours is internet facing then you may simply want to add an exception/rules for allowing https/TCP443. My server will ultimately have a public IP address that resolves to its public name (vpn.pnl.com) so I just need to allow the ports in. If your server does not have its own public IP address, then you may need to setup port forwarding instead. You will see later I’m also going to use TCP 80 (normal HTTP) to access my certificate services remotely, so I’ve got that open as well. You may want to access certificate services via HTTPS instead in a corporate environment.

21. On this server I’m simply going to disable the firewall > Start > Run > firewall.cpl {enter} > Turn Windows Firewall on or off > Set as appropriate.

Grant users SSTP VPN/Dial-in rights.

22. Make sure that any user who wants to access the SSTPVPN has had their Dial-in set to ‘allow access’.

Windows 2012 Server Install and Configure RRAS for SSTP

23. From Server Manager (ServerManager.exe) > Add Roles and Features > Next > Next > Next > Select > Network Policy and Access Services.

24. Add Features > Next > Next> Next > Next > Install > Close.

25. Back at Server Manager (ServerManager.exe) > Add Roles and Features > Next > Next > Next > Select ‘Remote Access’.

26. Add Features > Next > Next > Next > Tick ‘Routing’ > Next > Install.

27. Close.

Note: At this point you may see the warning that there are additional steps to take, (to configure routing an remote access), if so you can launch and then close this wizard because we will do it manually.

28. Close Server Manager > Open a new MMC > File > Add/Remove Snap-in > Certificates > Add > Computer account > Finish > OK.

29. Expand Personal > Certificates > All Tasks > Request New Certificate.

30. Locate the SSTP-VPN entry > Click the ‘More information required..’ link.

31. Change the Type to common name > Enter the public name of the SSTPVPN server > Add > OK.

Note: This will be the common name on the certificate, i.e. vpn.pnl.com, which will need a public A/Host record creating for it in your public DNS, (speak to your ISP or DNS hosting company). That way when your remote clients go to https://vpn.pnl.com they wont get an error, (providing you imported the root cert correctly on THAT machine).

32. Tick the certificate > Enrol.

33. Finish > Close the MMC.

34. Windows Key+R > rrasmgmt.msc > OK.

35. Right click the server > Configure and Enable Routing and Remote Access.

36. At the Wizard > Next > Next > Tick VPN > Next.

37. Select NIC1, In this case I’m unticking the ‘Enable security’ option, (or is disables RDP and locks the NIC down) > Next.

38. I’m going to use this server so select the bottom option > Next.

39. New > Create a range of IP addresses. (Note: You may need to exclude these from your existing DHCP scope) > OK > Next.

40. Next.

41. Finish > OK > OK > At this point you will see the services restarting.

42. Right click the server > Properties.

43. Security tab > Change the certificate to the one we created > Apply > Yes > OK > Close the console.

Windows Server 2012 – Connect to SSTP from a Remote Client

At this point I have the correct ports open on the firewall, and I’m on a Windows 7 client outside the corporate network.

44. Because we are using a self signed certificate, we need to get the client to trust it. We can give the user the root certificate, or they can connect and download it, here I’m connecting to the Certificate Services web portal. Note: Remember that’s on the same server.

45. Supply your domain credentials > OK > Download a CA Certificate > Download CA Certificate > Save As.

46. Put the certificate somewhere, and call it something sensible.

47. Now launch an MMC on the client machine, and add the certificate snap-in (for ‘computer account’).

48. Drill down to Trusted Root Certification authorities > Certificates > All Tasks > Import > Navigate to, and select the certificate you just downloaded.

Note: If you double click the cert and import it manually, then it gets put into the user accountNOT the computer account, and this will cause you problems. (Error 0x800b0109).

Registry Key Required for SSTP Access

The title is not really true, but as we are using a self signed certificate the client cannot check the CRL for the CA. Even with some purchased certificates you may need to to do this.

49. Open the registry editor and navigate to:

Windows Sstp Client Download

50. Create a new 32 bit DWORD called NoCertRevocationCheck and set its value to 1 (one).

Setup a SSTP VPN Connection

51. Open the Network and sharing Center.

52. Setup a new connection or network.

53. Connect to a workplace.

54. Use my Internet Connection.

55. Supply the Internet Address (that matches the common name you used above) > Next.

56. Supply your domain credentials > Connect.

57. Connected successfully.

Note: If it fails at this point, it usually gives you an error code you can Google, or it gives you the option of logging for you to troubleshoot.

58. Just to prove I’m connected, this client can ping the SSTP servers private address.

Related Articles, References, Credits, or External Links

Windows Sstp Client Software

NA