VPN to same IP range
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||||||||
|
Posted by S W on December 13, 2006, 2:00 pm
Please log in for more thread options This may be an FAQ, I'de be surprised if no-one else has had this problem! Our LAN is on a single subnet 192.168.15.0 We're running a W2000 RAS server for VPN. A client needs to VPN in and then remote desktop. He is on a LAN totally different location and company but with the same IP range. He can connect with a VPN no problem, but then can't see the server that he needs to RD onto. Is there a solution apart from one of us changing the IP range of our LAN? Thanks in advance, SW | ||||||||||||||||
|
Posted by Simon on December 13, 2006, 2:52 pm
Please log in for more thread options Never tried this, but I wonder if you could dual nic the server he needs to get to and give that another address (different subnet of course), then give him an address in that subnet when he vpn's in. Don't give the server a default gateway for that new subnet and it should still act ok. If you do have to change the server IP then go for something most people wouldn't use like a 172. address in case it ever happens again. simon | ||||||||||||||||
|
Posted by S W on December 13, 2006, 5:06 pm
Please log in for more thread options Simon wrote:
> S W wrote:
> >> Hi,
>> >> This may be an FAQ, I'de be surprised if no-one else has had this >> problem! >> >> Our LAN is on a single subnet 192.168.15.0 >> We're running a W2000 RAS server for VPN. A client needs to VPN in and >> then remote desktop. He is on a LAN totally different location and >> company but with the same IP range. He can connect with a VPN no >> problem, but then can't see the server that he needs to RD onto. Is >> there a solution apart from one of us changing the IP range of our LAN? >> >> Thanks in advance, >> SW >
> Hmm, > Never tried this, but I wonder if you could dual nic the server he needs > to get to and give that another address (different subnet of course), > then give him an address in that subnet when he vpn's in. > Don't give the server a default gateway for that new subnet and it > should still act ok. > If you do have to change the server IP then go for something most people > wouldn't use like a 172. address in case it ever happens again. > simon Sounds like its worth a try definitely! By a 172. address do you mean 192.168.172.? Thanks, SW | ||||||||||||||||
|
Posted by Simon on December 13, 2006, 5:42 pm
Please log in for more thread options S W wrote:
> Simon wrote:
>> S W wrote:
>> >>> Hi,
>>> >>> This may be an FAQ, I'de be surprised if no-one else has had this >>> problem! >>> >>> Our LAN is on a single subnet 192.168.15.0 >>> We're running a W2000 RAS server for VPN. A client needs to VPN in >>> and then remote desktop. He is on a LAN totally different location >>> and company but with the same IP range. He can connect with a VPN no >>> problem, but then can't see the server that he needs to RD onto. Is >>> there a solution apart from one of us changing the IP range of our LAN? >>> >>> Thanks in advance, >>> SW >>
>> Hmm, >> Never tried this, but I wonder if you could dual nic the server he >> needs to get to and give that another address (different subnet of >> course), then give him an address in that subnet when he vpn's in. >> Don't give the server a default gateway for that new subnet and it >> should still act ok. >> If you do have to change the server IP then go for something most >> people wouldn't use like a 172. address in case it ever happens again. >> simon >
Hi,
> Sounds like its worth a try definitely! > By a 172. address do you mean 192.168.172.? > > Thanks, > SW No A 172.X... Address. Most home routers use 192.x.x.x or even 10.x.x.x, I've not seen one that uses a 172 - http://en.wikipedia.org/wiki/Private_network simon | ||||||||||||||||
|
Posted by S W on December 14, 2006, 3:41 pm
Please log in for more thread options Simon wrote:
> S W wrote:
> >> Simon wrote:
>> >>> Hmm,
>>> Never tried this, but I wonder if you could dual nic the server he >>> needs to get to and give that another address (different subnet of >>> course), That's the easy bit! then give him an address in that subnet when he vpn's in. Not sure how I'd do that without upsetting the rest of the vpn users? >>> Don't give the server a default gateway for that new subnet and it
>>> should still act ok. >>> If you do have to change the server IP then go for something most >>> people wouldn't use like a 172. address in case it ever happens again. >>> simon >>
>> >> Sounds like its worth a try definitely! >> By a 172. address do you mean 192.168.172.? >> >> Thanks, >> SW >
Thanks for your help, and that was a useful link too.
> Hi, > No A 172.X... Address. Most home routers use 192.x.x.x or even 10.x.x.x, > I've not seen one that uses a 172 - > http://en.wikipedia.org/wiki/Private_network > simon SW | ||||||||||||||||
| Similar Threads | Posted |
| VPN to same IP range | December 13, 2006, 2:00 pm |
>
> This may be an FAQ, I'de be surprised if no-one else has had this problem!
>
> Our LAN is on a single subnet 192.168.15.0
> We're running a W2000 RAS server for VPN. A client needs to VPN in and
> then remote desktop. He is on a LAN totally different location and
> company but with the same IP range. He can connect with a VPN no
> problem, but then can't see the server that he needs to RD onto. Is
> there a solution apart from one of us changing the IP range of our LAN?
>
> Thanks in advance,
> SW