[RESOLVED] Setting up static routes on WindowsXP/Windows7 VPN workstation

Heyup

Hope some clever guru can help with this setup :

Scenario :

Site A is connected to Site B via fiber link. Site A can VNC to Site B, and Site B can VNC to Site A.

Now, we want to VPN in from the office to Site A. This works, we're able to access Site A's PC's no problem.

However, we need to VNC in to one PC on Site A, and, on this particular PC, we then VNC in to Site B.

Which is a bit cumbersome.

I want to set up static routing, so that we can VNC directly in from the office to Site B without having to use any of Site A's PC's at all.

Site A : 10.1.20.0/24, router IP 10.1.20.2
Site B : 10.1.16.0/24, router IP 10.1.16.2

Workstation VPN IP : 10.1.20.xx

I tried to add a static route manually, but failed.

The command I used was :

route add 101.20.2 mask 255.255.255.0 10.1.20.2 metric 1

It should work, no?

At the moment the VPN is down on the remote site, can't check it out.

Use port forwarding on the router at Site B. Choose a specific port, eg 3333, and forward it to the IP address of the specific PC you want to VNC into. Then from site A (or anywhere for that matter), you can VNC into the machine directly, via the port forward on the router.

You need to add a route on Site A Router to route all traffic going to 10.1.16.0 to route via 10.1.20.0 gateway.

The_Librarian said:

It should work, no?

Click to expand...

No
route add 101.20.2 mask 255.255.255.0 10.1.20.2 metric 1 .... huh?

besides the 101 and 10 mistype, you can't set a static route to itself, needs to have a GW

Oops, yep, thanks for the pointer

Working

Please post the WORKING solution

Thanks

Ok, I can connect via VPN now.

When I try to add a route :

route add 10.1.16.0 mask 255.255.255.0 10.1.20.2 metric 1

then it says

The route addition failed: Either the interface index is wrong or the gateway does not lie on the same network as the interface. Check the IP address table for the machine.




NOTE : this was done on the workstation accessing the other network via VPN.

Solved.

On the VPN server, add the following :

route add 10.1.16.0 mask 255.255.255.0 10.1.20.2 -p

the -p makes it persistent.