Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 441
  • Last Modified:

How to connect a client to host (SBS 2008) VPN on same IP scheme.

Is there something I can do in RRAS or some other setting that I can change to get VPN to work with same IP scheme as someone else?  I'm using WRT54G wireless Linksys router, SBS 2008 to host the VPN connection, and the typical people that are connecting are using vista.
0
easyworks
Asked:
easyworks
  • 2
1 Solution
 
tigermattCommented:

This isn't easily possible - if at all. The only way you could work around the issue is to use a static route on the client machine, which specifically states that any traffic directed to the server's IP should be sent over the VPN. This has many disadvantages: the first is that it is not easy to manage this or centrally push it from the server, it would need creating on each VPN client. Second, if the server's internal IP is also in use on the remote VPN client's LAN, then this will cause major problems and things will fail completely.

Due to the nature of a VPN (as you have found out) the routing component ideally requires two separate subnets for determining whether to route traffic over the VPN or keep it local to the VPN client's LAN. In this case, this is a classic example - and your best option would be to either change the IP scheme to a different subnet at the client end, or do the same at the server end.

I usually use an unusual subnet (one that isn't the default on most routers) on my networks which I deploy. For example, using 192.168.0.x is likely to get you into trouble, as many, many home routers use that scheme and they will all have issues using the VPN to the remote server.

-Matt
0
 
easyworksAuthor Commented:
Alright thank you... I'll try this out the server is almost out of the box i havent put it 100% up so i guess ill probably just go back and rebuild it because I cant just change IP so easily something always seems like its missing if i do try.
0
 
tigermattCommented:

Changing the IP address of a DC/Exchange/DNS server is always risky business. If the server isn't yet fully implemented I'd go for a rebuild.

Putting the server on a non-standard IP range will get you out of all sorts of trouble. :-)

-Matt
0

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now