Re: VPN routing from NAT to NAT
From: Jeffrey Randow (MVP) (jeffreyr-support_at_remotenetworktechnology.com)
Date: 04/30/04
- Next message: Jeffrey Randow (MVP): "Re: Mapping a Network drive & remembering the password"
- Previous message: Jeffrey Randow (MVP): "Re: VPN with 2 XP Home"
- In reply to: Bob: "Re: VPN routing from NAT to NAT"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 29 Apr 2004 19:55:29 -0500
Only problem is that how you would need to configure the routing
script so it will determine that posts sent to your local network go
to its gateway and posts to the remote network goes to the VPN
server... That's why it is easier to set up on different IP address
schemes... Most routers (including the Linksys) will allow you
specify a different network address (i.e., when I had a Linksys, I
configured it to use 192.168.3.x since my office network is
192.168.2.x and I accessed another network on 192.168.1.x)...
Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com
Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....
Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
On Tue, 27 Apr 2004 13:06:25 GMT, spam@spam.com (Bob) wrote:
>On Tue, 27 Apr 2004 00:09:07 -0500, "Jeffrey Randow (MVP)"
><jeffreyr-support@remotenetworktechnology.com> wrote:
>
>>You would definately want to re-subnet your networks... The easiest
>>way to do this is to make one 192.168.x.0, where x is any number from
>>0-254 other than 1. Or you can get a new subnet mask and split apart
>>the 192.168.1.x network into multiple subnets (much harder).
>>
>>The alternative is to hardcode routes to the specific IP addresses of
>>the computers you want to connect to with the "route" command...
>
>You do not have to do any of that. You are overly complicating what
>amounts to a simple fix, at least in the case of PPTP. In fact, with
>the very popular Linksys BEFSR41 router, you can't have two different
>subnets. The subnet is hardcoded to 192.168.1.X
>
>All you have to do is separate the subnet into two address regions,
>one for the LAN Adapter and one for the VPN Adapter.
>
>For example, I set LAN IP addresses below 192.168.1.100 and VPN IP
>addresses from 192.168.1.100 - 192.168.1.200. All addresses on my
>networks are static, so I never have a conflict. But if you want to
>use DHCP for assigning LAN IP addresses, just limit the range in the
>router to the address region for the LAN. I also set up the VPN Client
>to ask for a specific address in the range above 192.168.1.100. PPTP
>assigns 192.168.1.100 to the VPN Server since it is the first of the
>VPN Adapter range.
>
>Now I can use the HOSTS table, or set up windows that map to raw IP
>addresses, because those addresses never change. For those who might
>not be aware of how to set up access windows, go to Start|Run and type
>in the NetBIOS name in the form of a raw IP address. For example, if
>the VPN Server is 192.168.1.100,
>
>Start
>Run \\192.168.1.100
>
>[Note the double backslash, which is NetBIOS specific]
>
>will spawn a window showing all the shares on the VPN Server. You can
>shortcut that window and keep it on your Desktop for later use. It
>will always be valid since the VPN Server address will always be the
>same from one session to the next.
- Next message: Jeffrey Randow (MVP): "Re: Mapping a Network drive & remembering the password"
- Previous message: Jeffrey Randow (MVP): "Re: VPN with 2 XP Home"
- In reply to: Bob: "Re: VPN routing from NAT to NAT"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
