Client to site VPN in the right subnet

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Client to site VPN in the right subnet

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Client to site VPN in the right subnet
Client to site VPN in the right subnet
2014-11-16 18:25:54 - last edited 2021-08-21 04:28:23
Region : Argentina

Model : TL-ER6120

Hardware Version : V1

Firmware Version :

ISP :


Hello,

we've bought a TP-ER6120 Router and now we want configure VPN over PPTP for accessing our internal company network from different home offices through the internet.

( Admin's Home Office -> Any Consumer Router ) -> Internet over glass fibre -> ( Router with static IP (configurable by ISP only) -> TP-ER6120 as NAT Router -> Company Network )

(192.168.0.101 -> 192.168.0.1) -> Internet -> (212.112.232.63 -> 212.112.232.64 -> 192.168.74.0/24)


Our internal network has the ip range from 192.168.74.1 - 192.168.74.255, but in the VPN IP Address Pool it's not possible to set an IP Address Range in this subnet (e.g. 192.168.74.200 - 192.168.74.210). Our Cisco Router on another (and slower) internet connection has this option, but no Dual WAN, Load Balancing and only 100 Mbps.

If we chose another subnet in the address pool (192.168.75.100 - 192.168.75.200 for example) the configuration can be saved and we are able to connect to the network. Unfortunately we can't connect to our server ip 192.168.74.20 or another computer in the company network. In Routing Tab we've tried to set a static route with destination 192.168.74.0 (subnet 255.255.255.0) and next hop 192.168.75.0. A ping to our server still afford no response.

How can we access our internal subnet from an external home office?


Best regards
Sven
  0      
  0      
#1
Options
1 Reply
Re:Client to site VPN in the right subnet
2014-11-18 09:10:49 - last edited 2021-08-21 04:28:23
As I know, the current design is that IP Address pool must be different range from LAN IP address range.
But there is plan to improve it in future firmware as TP-LINK people said.
  0  
  0  
#2
Options