Add a static route to access a host on the client side of VPN

Paul

1/22/24, 8:17 PM

Remote server (Windows Server 2012 R2) connects to local router and after that the server is accessible from 192.168.22.104 as 192.168.170.254 without any manual actions from me.

Now I would like to access 192.168.92.3 from 192.168.22.104 and assume that I should add a route on the 192.168.92.1 machine for that.

I tried following commands:

route add 192.168.92.3 mask 255.255.255.0 192.168.170.254
route add 192.168.92.3 mask 255.255.255.0 192.168.92.1

Both result in an error:

The route addition failed: The parameter is incorrect.

What should the route add command look like in order to achieve the goal?

Note: actually there is also a physical network between remote server and its hardware router, but it is not shown here. Remote virtual machine also has an address in it. Client side router is the default gateway for both of the machines and I do not want to change the state of things. It is super important that remote virtual machine has all its traffic over its current default route and that it uses the 192.168.92.x addresses only to communicate with 192.168.22.x network. 192.168.92.x is a virtual network in Hyper-V and exists only between the VM and VM host.

181

0 + 0

networking

windows

vpn

routing

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Add a static route to access a host on the client side of VPN

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.