Link to home
Start Free TrialLog in
Avatar of Isaias Perez
Isaias PerezFlag for United States of America

asked on

Server 2012 R2 VPN solutions

So let me explain what type of physical server configuration i have going on. So i have a Linksys Router EA6900 that is the Gateway to our Network. The Router is connected to our switch. Our server has two nics that are both connected to our switch for redundancy and load balance (Nic Teaming) The server is a domain controller, File server and DHCP/DNS Server. I have read that to use VPN you have to have a cat 5 from the Time Warner Modem itself straigt into a Nic on the server with a static IP address and routing/firewall instructions to make it work. My question is, are there any VPN solutions that i can use with my current physical network configuration? Everything is working just right and i dont want to switch things around. Thank you.
Avatar of Kash
Kash
Flag of United Kingdom of Great Britain and Northern Ireland image

NIC teaming would allow you to share one IP.
You could probably use your server for RAS.
Install and set up necessary NAT'ing on the linksys and should be good to go.
Consider replacing your Linksys EA6900 with an economical VPN router (Juniper Netscreen SSG5 or Cisco RV325). This is what I do and it is easier over the long run.
ASKER CERTIFIED SOLUTION
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I can only agree to above said.

Having one NIC connected to the Internet directly makes it easier to set up RRAS (what Windows Server uses for dial-in and VPN), but is no requirement. However, having a static public IP or DNS name entry is required, as traditional VPNs are point-to-point connections, and at least one partner needs to be reachable from Internet (IP or DNS name).

If you have dynamic public IP on both ends, you can set up one to use a Dynamic DNS Service which assigns a static name to your dynamic IP, and so makes it reachable.

Is this thought as a dial-in type of service for multiple users, as a site-2-site connection, ...?
Whatsoever, don't expect to get anything which "just runs" with your current setup. It is always a question of either investing man power (and time), or hardware, or both ;-).