Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 107
  • Last Modified:

VPN Server (Windows Server 2008 R2) using “Network Policy and Access Services”

I'm attempting to set up a VPN server on a virtual machine.

I followed the steps here:
http://www.thomasmaurer.ch/2010/10/how-to-install-vpn-on-windows-server-2008-r2/

Right now this is only with ONE NIC on the VM, where I have a static pool of private IPs.  Basically I followed this guide:
http://www.thomasmaurer.ch/2010/10/how-to-install-vpn-on-windows-server-2008-r2/


I am able to connect to the VPN, and I can ping 10.10.10.1 for example.

The issue is that I cannot connect out to the Internet through the VPN.


I'm assuming I probably need add a 2nd NIC but I'm not sure how to modify the configuration exactly.


The end result is when I'm on the VPN from say, my iPad or laptop... I want my public IP (ie - whatismyip.com) to show up as the IP of the VM.


I do have the capability to add another NIC and even to add another public IP to the VM if needed.


Just need some guidance in the rest of the setup, based on what I did so far (article above).


Thank you
0
Vas
Asked:
Vas
  • 2
1 Solution
 
VasAuthor Commented:
UPDATE:

I am able to get this working if I add a two public IPs to the NIC, and then set the range of static IPs to the range of the two public IPs.

The 2nd IP is assigned to my iPad when testing.


So I guess my question is... is there anyway to do this with the VM having only one Public IP,  or is it necessary to have multiple public IPs to make this work?
0
 
lasfraCommented:
The normal idea with a VPN server is that you should be able to reach your internal network from internet.
So what do you mean with:

“I am able to connect to the VPN, and I can ping 10.10.10.1 for example
The issue is that I cannot connect out to the Internet through the VPN.”

The VPN server should have 2 NICs, one NIC facing the outside and on NIC facing your internal network. This is true both for VMs and for physical hosts.
If you install a VM as a VPN server the VM should have 2 NICs. If your physical server has a NIC facing internet, each machine using this NIC has to have a unique IP address. So the VM and the physical server can not share the same IP address, but the can share the NIC.
0
 
VasAuthor Commented:
I was able to make it work with one NIC,  what I had to do was set the scope of the IPs to assign by the VPN service to additional public IPs.   I can connect to the VPN now and my public IP is shown as the public IP assigned by the VPN server.

What I haven't been able to do is set up an additional VPN user.  For testing right now, the current VPN user is the Administrator account, with granted "dial-up" privileges.

I created a second user, and even added it to the administrators group, gave it the same "dial-up" privilege (so right now there's really nothing different about this 2nd user in how it's configured as the administrator user)

The Administrator user can connect, but the new user can't.  No error, nothing in any logs, it just disconnects right away when trying to connect.
0

Featured Post

Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now