Welcome to ISAserver.org

Cannot RDP when destination subnet is the same as home network subnet

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> VPN >> Cannot RDP when destination subnet is the same as home network subnet

Page: [1]

Message

<< Older Topic Newer Topic >>

Cannot RDP when destination subnet is the same as home ... - 19.Dec.2007 4:10:38 PM

jlestrange

Posts: 16
Joined: 1.Nov.2006
Status: offline

Hi,

We are running into a problem here when people sign into the VPN and try to RDP a PC with the same subnet that is handed out by their router.

For instance:

My router at home has a DHCP scope of 192.168.2.x. Therfore I cannot connect to PCs that are in the 192.168.2.x subnet at work. The only way to work around this is to do a persistent route with the VPN Client address as the default gateway on 192.168.2.x addresses. I don't want to tell people to reconfigure their DHCP scope at home either.

Any help would be great.

Thanks,
Joe

Post #: 1

Featured Links*

RE: Cannot RDP when destination subnet is the same as h... - 19.Dec.2007 5:06:09 PM

justmee

Posts: 505
Joined: 14.May2007
Status: offline

Hi Joe,
There is no real solution for your problem.
The subnets must be different.
You should have choosed a less "common" subnet at work. 192.168.2.0/24 is a pretty used one so such conflicts are imminent.
If you would be on the road you should carry a small NAT device with you to prevent such conflicts.
You might like to read(although not directly related to your problem):
http://blogs.isaserver.org/shinder/2006/06/28/vpn-solution-for-hotel-networks-on-the-same-network-id-as-corpnet/
Probably the most simple solution(or not