1

Setting up a VPN on Windows 2008 R2, should I use PPTP or SSTP?

view story
linux-howto

http://serverfault.com – I'm setting up a VPN test server, on Windows 2008 R2. I seem to remember that PPTP isn't ideal, as on a Cisco firewall you need to allow quite a large range of ports open (with the GRE protocol too?) Anyway, my vague memories of this aren't brilliant, so I would like to know, what's the more secure protocol for setting up remote VPN access (from users dialling in from home, so not a VPN tunnel or anything). (HowTos)

u85500's picture
Submitted by u85500 on 10/03/2012

Stories similar to Setting up a VPN on Windows 2008 R2, should I use PPTP or SSTP?

I’m trying to set up a PPTP VPN connection on a Windows 2008 R2 SP1 Server with a public IP. One of the steps is to allow GRE (Generic Routing Encapsulation) 47 direct access to the server. How can I make an exception in Windows Firewall, when it isn’t an actual port, but a protocol?

Hi, I need help getting a standard PPTP VPN connection working. I have the Network Manager plugins installed, and have in the past connected to this VPN fine but now (since upgrading to Karmic) I get errors relating to GRE protocol.

I own a Windows Server 2003 VPN server which my clients connect to for accessing the local network..

I have configures the RRAS to use the RADIUS authentication and accept connections.

The PPTP protocol works great and does all that is expected. But the L2TP protocol has some problems.. When I try to connect to the server it just stays on Connecting to domain.com...

I'm setting up a fileserver, and I want lots of clients to easily access it. Up to now I've always used SSHFS to share between different PCs, but since I'm setting up a single fileserver, I'm looking for other common alternatives. Up to now I've seen:

AFS: It seems it has no security, traffic is unencrypted, so it would require an SSH tunnel.

We've a Windows Server 2008 host on VMware ESXi 4 and want to isolate it from the rest of the network. That is, I want no traffic from the Windows Server 2008 to be allowed on the normal network.

I have RRAS running (Windows 2008 R2) on my server to provide PPTP VPN connection in order to share the server Internet with users.

Users are able to connect to the server and I can see them on Remote Access Client List (RRAS), but when they connect, status is NOT a NAP-Capable and they are unable to connect to the internet.

I don't need NAP and anything like that at all.

Following the recent security advisory, I'm reconfiguring our VPN servers and having trouble.

We're using Windows 2008 R2 server for VPN services, running RRAS and NPS on the same server and configure it to use PEAP-EAP-MSCHAPV2 authentiation for all tunnel type(PPTP, L2TP, IKEv2, SSTP), which previously allowed plain MSCHAPv2.

But Apple products, MacOS and iOS cannot connect to VPN after this c

I run a small business network and the last couple of days I have been setting up some equipment to add VPN capabilities to our network. I've got the following set up:

Windows 2008 R2 with RRAS - 172.22.200.50 Cisco RV082 router - 172.22.100.1 / 172.22.200.1

The Cisco router only support DHCP on a single class C network; 172.22.100.0/24.

I'm successfully authenticating and connecting to a SSTP VPN (on windows 2008) from my windows 7 machine, but for some reason, the connection is disconnected about a 1-2 seconds after it's established.

I've done the following:

Defined a SSTP VPN on my windows server 2008. Defined the same machine as CA. Issued the needed certificates and published them on the client. I'm currently testing this