Shara on the same machine with an OpenVPN server behind a router - is it possible to set the identity of the addresses of the shares in the local network and the VPN subnet?

Question

openvpn

And now it's a little clearer. I have a machine (WS2008R2) on which an OpenVPN server is installed and a share is organized on the same machine. This machine (hereinafter referred to as the server) is networked with several other machines by a router and has the address 192.168.1.104 in this network. All this network is connected through a router to the Internet. OpenVPN is running on the server, the server address is 192.168.2.1 in its subnet. From a client connected to this subnet, I have access to the resources of the router's local network (192.168.1.X) and to the Internet, that is, everything works. However, if I use the local network address (192.168.1.104) to access the server resources, and not its address in the OpenVPN subnet (192.168.2.1), then the connection speed and its stability drop sharply. That is: the connection to \\192.168.2.1\Video works almost perfectly, but \\192.168.1.104\Video has to wait several minutes, while the explorer opens the folder, while the explorer often freezes or gives a message that it can't connect. Similarly with VNC - access to 192.168.2.1 gives a normal broadcast, and to 192.168.1.104 - a picture that does not respond to any actions. At the same time, access to other resources of the local network 192.168.1.0 works without problems. Tracert for 192.168.1.104 shows three hops, the first two of which time out (the server itself and the router, I believe). Actually, the question itself is whether it is possible to somehow convince the server that accessing 192.168.1.104 from the tunnel subnet is the same as accessing 192.168. do you like these loops? 1 gives a normal broadcast, and to 192.168.1.104 - a picture that does not respond to any actions. At the same time, access to other resources of the local network 192.168.1.0 works without problems. Tracert for 192.168.1.104 shows three hops, the first two of which time out (the server itself and the router, I believe). Actually, the question itself is whether it is possible to somehow convince the server that accessing 192.168.1.104 from the tunnel subnet is the same as accessing 192.168. do you like these loops? 1 gives a normal broadcast, and to 192.168.1.104 - a picture that does not respond to any actions. At the same time, access to other resources of the local network 192.168.1.0 works without problems. Tracert for 192.168.1.104 shows three hops, the first two of which time out (the server itself and the router, I believe). Actually, the question itself is whether it is possible to somehow convince the server that accessing 192.168.1.104 from the tunnel subnet is the same as accessing 192.168. do you like these loops?

Answer 1

You would draw a picture. For example, it is quite difficult for me to read and understand this.

1. Check that routing is enabled on WS2008R2.
   
2. Publish VPN clients route to the server.
   server 192.168.2.0 255.255.255.0
   push "route 192.168.1.104 255.255.255.255"
   You didn't say anything about the client's subnet. Whether it is routed or not, because if it is routed, you will need to add its network to the server config with the route option and ccd config to the certificate that is responsible for the router.