Routing between remote servers over VPN?

Question

VPN

Good afternoon!
Please help.
I re-read the article several times, did everything, it seems to me, correctly, but the routing does not work properly.
There is an office and a remote warehouse.
The office has: router => switch 48 ports => main domain controller wines 2008r2, many users from the switch, network 192.168.1.0, vpn server address 10.10.3.1 raised, local server address 192.168.
The warehouse has: a router => a switch of 48 ports => a wine server 2008p2 (which must be added as a second domain controller, but due to the lack of routes it does not work yet), a lot of users from the switch, network 192.168.0.0, vpn server 10.10 is raised. 3.100, server-local address 192.168.0.188.
It is necessary that the user from the office with the address 192.168.1.43 can log into the computer of the warehouse user with the address 192.168.0.56.
The servers connected to each other via vpn without problems, from 10.10.3.1 I go to 10.10.3.100 and back.
In the warehouse on the server, I write "route add 192.168.1.0 mask 255.255.255.0 10.10.3.1" and I can log in from the warehouse server at 192.168.1.121, i.e. to the office server. This is good, but I can’t go to 192.168.1.43, but I need it.
In the office on the server I write "route add 192.168.0.0 mask 255.255.255.0 10.10.3.100", but I can't log in from the office server at 192.168.0.188, i.e. the warehouse server goes to the office server via 192 networks, but the office server does not go to the warehouse server, it turns out one-way communication, but it is necessary in both directions.
Also, on the office user, I wrote "route add 192.168.0.0 mask 255.255.255.0 10.10.3.1", but it does not go to the warehouse server.
I can't understand where I'm wrong... Do I need to specify routes between vpn networks and local networks inside each server, although I tried it - it didn't help...
Help, please.

Answer 1

You need the local address of the gateway through which the connection will go. Those. the client in the subnet 192.168.0.0/24 needs to register [where to go] and [through what to go]
route add 192.168.1.0 mask 255.255.255.0 192.168.0.188
If the VPN server is the main (primary) gateway for network clients, then the route can be registered on it and don't do it on clients.