Ananth wrote

We would like to establish secured Machine to Machine VPN with the following features:
1. Should support secured Site-to-site VPN, Remote access VPN using pre-shared key & Certificate based (L2TP VPN, PPTP VPN, SSL VPN, IPsec) on Windows operating system (Windows 7, 10, Windows Server 2008, 2012, 2016) platforms.
2. Should provide minimum 100 concurrent VPN sessions.
3. Provision for two way communication between any client-to-server or any client-to-client, connected on the VPN
4. Should be able to assign static IPs for each client/ server. VPN connection should retain the pre-assigned static IP created while creating the user.
5. In case of communication failure or network failure, the VPN should automatically reconnect and rejoin VPN when the communication is re-established without user intervention.
6. VPN Should auto start when the PC/ Workstation/ Server is restarted without waiting for user to login.
7. Should support tunneling as well as data encryption.
8. Should be able to connect using Remote Desktop to any of the machines connected in the VPN network.
Request to suggest best cost effective solution for the above requirement.

TP-Link SMB VPN Router can meet the option 1,3,7,8.

Thanks for the reply.

Can I met the following conditions, if I change the spec as below:

A centralised Client should be able to access multiple servers located at different places using VPN Tunnel (TCP/IP communication through this tunnel). The servers at remote location has to be binded to a static IP, sothat the client at the centralised location can connect to this IP and port no and access the data.

Do we need to have public IP at all the locations? (I prefer to have only one public IP at centralised location and uses a pre assigned key with a static IP as used in case of OpenVPN)

Incase of communication break, does VPN automatically reconnect when the link become OK?

How many concurrent connections the centralised client can have?

Thanks

Ananth wrote

Thanks for the reply.

 

Can I met the following conditions, if I change the spec as below:

A centralised Client should be able to access multiple servers located at different places using VPN Tunnel (TCP/IP communication through this tunnel). The servers at remote location has to be binded to a static IP, sothat the client at the centralised location can connect to this IP and port no and access the data.

 

Do we need to have public IP at all the locations? (I prefer to have only one public IP at centralised location and uses a pre assigned key with a static IP as used in case of OpenVPN)

Incase of communication break, does VPN automatically reconnect when the link become OK?

How many concurrent connections the centralised client can have?

 

Thanks

You need to have public IP at all the locations. Because your centralised client need to access the server at remote location, you need the public IP of remote location to build the VPN tunnel.

If the VPN tunnel disconnects, it will try to reconnect automatically.

About how many VPN tunnels TP-Link router support, you can see their website. Like ER6120 supports 100 IPsec VPN Tunnels, 50 PPTP VPN Tunnels and 50 L2TP VPN Tunnels. 

https://www.tp-link.com/en/business-networking/vpn-router/tl-er6120/#specifications