VPN & Adding New Firewall

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

We have Remote Access set up and functioning very well.
Users log in to our network with the LTTP connection
built into XP. The remote users connect to our external
firewall (I'll call it VPNr) which routes the port 1723
connections to the RAS server internally.

Today I set up a second firewall (I'll call it New), the
intent was to have internal users go through this one and
leave the one that handles VPN traffic to the remote
users. Changes I made were as follows:

on RAS server: Changed "Router" in DHCP Scope Options
from the internal IP of VPNr to that of New. Both
routers are on the same subnet, but each has its own
valid external IP.

From the inside, things worked great. I could get to the
internet through New when obtaining my IP/Gateway
automatically. I could also set a static IP from the
inside to go out through VPNr.

However, remote users could no longer connect. I had not
changed anything on that router. What would have caused
this to occur? Was it changing the Router IP in scopes
to the New router that blocked remote users out? They
aren't set to use the default gateway on the remote
network, so I didn't think it would actually use that.

Anyone have any insight? Thanks,

Ben
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Did you reset the original firewall (VPN gateway) to the new default
gateway address? This shouldn't make a difference, but its hard to
tell with third party devices... :(

Jeffrey Randow (Windows Networking & 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 Wed, 8 Sep 2004 11:29:27 -0700, "Ben Creel"
<anonymous@discussions.microsoft.com> wrote:

>We have Remote Access set up and functioning very well.
>Users log in to our network with the LTTP connection
>built into XP. The remote users connect to our external
>firewall (I'll call it VPNr) which routes the port 1723
>connections to the RAS server internally.
>
>Today I set up a second firewall (I'll call it New), the
>intent was to have internal users go through this one and
>leave the one that handles VPN traffic to the remote
>users. Changes I made were as follows:
>
>on RAS server: Changed "Router" in DHCP Scope Options
>from the internal IP of VPNr to that of New. Both
>routers are on the same subnet, but each has its own
>valid external IP.
>
>From the inside, things worked great. I could get to the
>internet through New when obtaining my IP/Gateway
>automatically. I could also set a static IP from the
>inside to go out through VPNr.
>
>However, remote users could no longer connect. I had not
>changed anything on that router. What would have caused
>this to occur? Was it changing the Router IP in scopes
>to the New router that blocked remote users out? They
>aren't set to use the default gateway on the remote
>network, so I didn't think it would actually use that.
>
>Anyone have any insight? Thanks,
>
>Ben