Configuring SSL VPNs for Secure Public-Terminal Connections

Secure Sockets Layer (SSL) VPNs offer secure remote network connections from public Internet Access Points (APs). SSL VPNs create secure connections regardless of what client the user has or what proxy servers, firewalls, or Network Address Translation (NAT) devices stand between the user and the VPN server. Windows Vista SP1 and Windows Server 2008 are the first Microsoft OSs to natively support SSL VPNs. Microsoft incorporated its new VPN protocol, Secure Socket Tunneling Protocol (SSTP), into Vista SP1 and Server 2008 to enable secure network connections through HTTP Secure (HTTPS) without requiring you to install additional client software. Unlike traditional PPTP and L2TP/IPsec VPNs, which aren’t reliable over public networks, SSTP can establish virtual network connections through public networks because of HTTPS's widespread usage. If you’re running Vista SP1 and Server 2008 and want to take advantage of the new, more secure SSL VPNs, you’ll need to perform a series of configuration steps to enable your remote users to connect via SSL VPN. Here I’ll take you step-by-step through an SSL VPN installation and configuration, but first let’s briefly review the shortcomings of traditional PPTP and L2TP/IPsec VPNs and take a quick look at SSTP. . . .