A
A
Alex_Buzz2017-06-26 15:39:59
VPN
Alex_Buzz, 2017-06-26 15:39:59

Mikrotik VPN L2TP+IPSec server - Windows clients. Routing?

Good afternoon, colleagues!
There is Mikrotik at the head office acting as a L2TP+IPSec VPN server. Windows clients connect to it. Behind this Mikrotik is a local network (for example 192.168.0.0/24) There is a file server in the local network. L2TP+IPSec VPN server clients are given addresses from the 192.168.0.0/24 network (they do not intersect with the DHCP pool). Thus, it was possible to let VPN L2TP + IPSec clients into the local network and give access to the file server (the "Use the default gateway on the remote network" checkbox in the Windows client settings is not suitable for my situation)
This Mikrotik also acts as a PPTP VPN server. Other Mikrotiks in branches (Site-to-Site), as well as Mikrotiks in the data center are connected by PPTP clients. There is a terminal server in the data center. Static routing between branches, data center and head office is configured. Thus, local network clients in branches (for example, 192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24, etc.) and the head office have access to the terminal server and file server (physically located in different networks ), but L2TP+IPSec VPN server clients only see the file server. I don’t understand why ... After all, there is routing from the local network of the head office (where L2TP + IPSec server clients connect) to the local network of the data center ...
Is it possible to connect Windows clients so that they would go to the remote network of the data center via VPN L2TP+IPSec server in the local area network of the head office without manually setting the routing in Windows?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
D
Dmitry Tallmange, 2017-06-26
@Alex_Buzz

checkbox "Use default gateway on remote network" in Windows client settings is not suitable for my situation

That is why the specified hosts do not see any other subnets. Connecting adds ONE route to 192.168.0.0/24 through the remote gateway. The remaining subnets are searched for by the default route.
There are only two ways out, whatever one may say:
1. Let all traffic go through a remote gateway, that is, through vpn
2. Register routes locally, on Windows machines

K
Konstantin Stepanov, 2017-06-26
@koronabora

Tracing to the studio.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question