Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hello,
I have a VPN connection to another company which is working great.
Now I would like to take over a server (RDP) on IP 10.0.10.32 on the
other company's network, but when I try that, RDP makes a connection
with the server 10.0.10.32 on my local network. How can I RDP to the
server on the other network?Thank you!

I would like to take over a server (RDP) on IP 10.0.10.32 on the other company's network
Maybe it's just a mistake in grammar but, when you say "take over" do you mean hack it? Or do you just mean connect to it and administer it?

Normally a vpn "takes over" your connections.
Rather a security issue it doesn't. Might check that first.Well, the information of the IP address, subnet mask and gateway is the couse that the packets are directed to travel in normal instances. See what that is.
I read it wrong and answer it wrong too. So get off my case you goober.

"but when I try that, RDP makes a connection
with the server 10.0.10.32 on my local network. How can I RDP to the
server on the other network?"So, the local and remote subnets are both "10.0.10.x/24"??? A VPN won't work, if you have overlapping subnets. Reason being, since your VPN client is on 10.0.10.x/24, your computer will expect all 10.0.10.x machines to be local, thus, the traffic will not be routed out the VPN "virtual interface".

This is not entirely true.
You may absolulely have a VPN connection between you identical subnets, however you will run into trouble if you have nodes on each network which have the same IP Address. The way you are describing your problem, it seems as though you may have two hosts with an IP of 10.0.10.32.
What type of VPN do you have? PPTP using the integrated Windows client? If so, check your advanced TCP/IP properties, and see if the option is checked to "use default gateway on remote network".
Also try this. Before you connect to the VPN, from a command prompt issue the command "route print". Copy and paste this routing table to a document. Connect to the VPN, issue "route print" again, then copy this information to the same document. See if you notice a change in the route for 10.0.10.0 255.255.255.0. Make a note of which default gateway and/or interface address is being used in both cases.
If there is no way around giving the RDP Server on the far-end network a different IP address, and there is a host on your local LAN with that same IP, you could modify your routing table each time you connect to the VPN to force packets destined for 10.0.10.32 out the virtual VPN interface. Show me the current routing table entries via the instuctions above and we can do from there.

Okay, I agree, I forgot about "use default gateway on remote network". However, you won't be able to access any of your local network resources, once this option is enabled!
Also, there is also 1-to-1 NAT and dynamic nat, which can be configured, to masquerade the network as something else.But for the sake of keeping things simple.....

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |