R
R
Rad1us2016-10-06 10:33:40
Computer networks
Rad1us, 2016-10-06 10:33:40

Why doesn't accessing shared folders in Windows through VPN work?

Office network on Windows, all computers in the workgroup. All computers on the network have their own shares, with full access for everyone. The security policy on all computers is the same. The network address is 192.168.0.0/24. The network has Mikrotik, which acts as a PPTP server.
The remote office has Mikrotik, which is a PPTP client. An EoIP tunnel has been raised between the routers. The network address of the remote office is 192.168.1.0/24
With this configuration, the computers of the remote office see only a part of the shared folders of the main office. The rest are not visible ("network path not found" error). Ping, 1Ska and other works well. What could be the problem?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
K
Konstantin Stepanov, 2016-10-06
@rad1us

Raise a level2 tunnel to open vpn, or you need to configure a wins server.

H
HawK, 2016-10-06
@HawK3D

In general, it should be organized like this:
- A tunnel between routers is up and running;
- An EoIP tunnel has been raised over the tunnel at both ends;
- Local interfaces and EoIP tunnels are combined into a bridge on each router;
- 2 DHCP servers are configured on both routers, you need to specify your bridge interface as the DHCP interface. DHCP network should be a single 192.168.0.0/16 in your case, it is specified in the settings of both DHCP servers, but the ranges (pool) of issuing addresses should be non-overlapping, included in the designated subnet. For example, 192.168.0.2-192.168.0.255 on one router and 192.168.1.2-192.168.1.255 on the second, in your case.
- It is wrong and reckless to create one DHCP for the local and remote subnets - in the event of a tunnel break between routers - on the side where there is no DHCP, the lease terms will expire, with all the consequences.
- Extra broadcast can be blocked using /interface bridge filter.
- Be sure to create a rule that blocks DHCP requests between remote networks, for example:
/interface bribge filter
add action=drop chain=forward comment="Drop DHCP requests over EoIP bridge" disabled=no in-interface=eoip-tunnel1 ip- protocol=udp mac-protocol=ip src-port=68
In this way, you can combine more than two remote networks, building an optimal topology. Works without problems, broadcast traffic is negligible.
PS Instead of an EoIP tunnel, it is preferable to use VPLS. In my settings, I started from the presentation
of Dmitry Kuznetsov, in fact, everything turned out to be a little simpler , I will give the differences in my settings: vpn-interface itself, or create a bind for the vpn-client so that the interface in the route is not replaced by unknow when reconnecting.
- It is enough to add only "empty" bridges to the list of LDP interfaces, you do not need to add vpn interfaces.
After switching to VPLS, I noticed some "revival" of the network and an increase in the maximum speed when downloading files.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question