Remote desktop within a VPN

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi There,

Scenario:
Client has a small LAN based around a Win 2003 SBS server with a local IP
range of 192.168.0.*

On one of the machines, the user has to connect to a remote location to run
a program. Following the provided instructions we set up the VPN to the
remote location which connects fine. Onc ethe VPN is connected the user is
required to used RDP to connect to a PC on the VPN network.

Problem:
The target PC on the remote network has an ip of 192.168.0.11. As this is
the same range as the local range and there is a PC with that address
assisgned locally it tries to connect to the local PC. We have even tried
using the remote pc name rather than IP address to no avail.

Is there a switch of command to force the RDP session to connect through the
VPN side rather than the local network?

Is this possible?

Thanks

Billy Gareth
 
Billy Gareth said:
Hi There,

Scenario:
Client has a small LAN based around a Win 2003 SBS server with a local IP
range of 192.168.0.*

On one of the machines, the user has to connect to a remote location to
run
a program. Following the provided instructions we set up the VPN to the
remote location which connects fine. Onc ethe VPN is connected the user is
required to used RDP to connect to a PC on the VPN network.

Problem:
The target PC on the remote network has an ip of 192.168.0.11. As this is
the same range as the local range and there is a PC with that address
assisgned locally it tries to connect to the local PC. We have even tried
using the remote pc name rather than IP address to no avail.

Is there a switch of command to force the RDP session to connect through
the
VPN side rather than the local network?

Is this possible?

Thanks

Billy Gareth
Click to expand...

The issue is the subnets are the same. You would need to change the subnet
at either your location or the remote location to something other than the
192.168.0 subnet.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Hi,
Thanks for your response.

I was hoping for a more convenient solution than changing around my subnet
but if that is the only way then I guess that is what it will be.

Thanks again.

BG
 
Sooner Al said:
The issue is the subnets are the same. You would need to change the subnet
at either your location or the remote location to something other than the
192.168.0 subnet.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
Click to expand...

Wouldn't changing the subnet mask accomplish the same thing? Then connecting
to the remote machine would use 192.168.0.11:255.255.0.0 (assuming the mask
was changed to 255.255.0.0)?

Nill
 
Back
Top