[TL-R600VPN] L2TP/IPSEC for connecting 2 distant subnets (no NAT wanted)

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

[TL-R600VPN] L2TP/IPSEC for connecting 2 distant subnets (no NAT wanted)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
[TL-R600VPN] L2TP/IPSEC for connecting 2 distant subnets (no NAT wanted)
[TL-R600VPN] L2TP/IPSEC for connecting 2 distant subnets (no NAT wanted)
2018-10-22 15:52:13 - last edited 2021-04-20 11:22:49

Hi !

 

I'm trying to connect a TP-LINK TL-R600VPN (client) to a Microsoft Windows Server 2016 (L2TP and IPSEC VPN server).

 

In the VPN client, when I choose "NAT" working mode everything works properly. I can connect to my Windows Server shares and so on. But in the other way it doesn't work beacuse of the NAT mode. So I just change the working mode from NAT to Route. I can see the IPSEC SA and L2TP tunnel but it doesn't work anymore, in any way. Local IP and remote local IP are correct but I can't ping them.

 

Any idea of what I shoud do to make it work ?

 

Thanks a lot for your time !

 

Seb

 

 

 

  0      
  0      
#1
Options
2 Reply
Re:[TL-R600VPN] L2TP/IPSEC for connecting 2 distant subnets (no NAT wanted)
2018-10-22 15:54:51 - last edited 2021-04-20 11:22:49

Small change : I can ping the local IP but no the remote local IP.

  0  
  0  
#2
Options
Re:Re:[TL-R600VPN] L2TP/IPSEC for connecting 2 distant subnets (no NAT wanted)
2018-10-23 14:56:44 - last edited 2021-04-20 11:22:49
When you setup the router as client mode, it still work in LAN to LAN VPN mode. Maybe you can check if your windows server also supports LAN to LAN mode and has the right routing entries.
  0  
  0  
#3
Options

Information

Helpful: 0

Views: 1516

Replies: 2

Related Articles