How to correctly register the route windows 2012 r2?

Question

Network administration

There is a wine server 2012 r2
on it LAN network looks to the network
192.168.0.5
255.255.255.0
192.168.0.1
and the VipNet network looks to another network
10.2.201.4
255.255.255.0 .255.255 10.2.201.1 1 I raise it on this server (routing and remote access), after some manipulations, I notice that 10.61.100.51 is not pinged on the server. It looks like when you raise "routing and remote access" then the route added via route add stops working (please correct if it's wrong).
To ping 10.61.100.51 I add this route through the routing and remote access shell.
From the server starts to work, pings go up to 10.61.100.51.
--------------
I write route add 10.2.201.0 mask 255.255.255.0 192.168.0.5
on the client and it pings from the client, like the VipNet interface itself 10.2.201.4 and further 10.2.201.1 . it turns out routing earned, everything is buzzing.
But on the server there is a route that 10.61.100.51 sends through 10.2.201.1 and it pings from the server, as I wrote above.
Now the task is to get to 10.61.100.51 through the server,
I do route add 10.61.100.51 mask 255.255.255.255 192.168.0.5 and it does not work.
then I think that if 10.2.201.1 is pinged from the client (which is routed through the server), then I will try to register the route as on the server, for example, through 10.2.201.1 (After all, it is available)
I do route add 10.61.100.51 mask 255.255.255.255 10.2.201.1 But no result.
The question is how to make routing through the server, from the client, to the IP that itself is routed on the server.

Answer 1

I read it five times and I don't get it! What for generally something to write on the client? It must receive all zeros and routes from the gateway.
All these thoughts of yours are easily drawn with three lines. And you're here "I thought" "I did." Why the hell do we need this information if it doesn't work?

Answer 2