1 server with RRAS with 2 networks

I've got a question about setting up RRAS on a server that has 2 nics and is
on 2 networks.

I've got one server that has 2 nics in it. One for the internal network,
and another for a dedicated line to a client. If I'm on the server and have
both nics enabled, everything works great. In fact, I can remote into the
box and use it from other windows boxes on the internal network and can
access the client network.

The problem lies when I try to VPN into the box from the internet. If the
2nd nic (for the client network) is enabled I'm unable to establish a vpn
connection into the box. If the 2nd nic is disabled, I can make the vpn
connection with no problem. When the 2nd nic is disabled, I can make the
connection, remote into the box using it's internal IP and then enable the
client network and perform my tasks.

I have a feeling I need to setup a static route but I'm not sure. Any
ideas?

The server is setup this way:
Windows 2003 Professional SP1
Internal nic: 192.268.1.252 and gateway 192.168.1.1
Client nic: 192.168.9.5 and gateway 192.168.9.1

RRAS is setup using internal nic
Port 1723 is opened on the Linksys router to allow PPTP access

Help is greatly appreciated.

Does the internal NIC have a default gateway defined? If it does, remove
that. Next, you will need to setup a static route to reach your internal
network from the RRAS server.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Thanks for the reply Todd.

I erased the gateway from the 192.168.9.5 NIC.
I added a static route of 0.0.0.0 mask 0.0.0.0 192.168.9.1
From the server itself, I can ping the remote network with this setup.
That's good.

If I try to vpn into the box using our external IP, (port forwarded to this
box using the Linksys router) I am unable to connect.

If I disable the interface, then I can vpn in with no problems. That then
allows me to RDC to the desktop, ENAB:LE the interface and then I'm able to
work on the remote network.

It still seems like I've either incorrectly setup the static route or I need
an additional route...or something.??






"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Does the internal NIC have a default gateway defined? If it does, remove
> that. Next, you will need to setup a static route to reach your internal
> network from the RRAS server.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>

Anyone?

"Mark Rodgers" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Thanks for the reply Todd.
>
> I erased the gateway from the 192.168.9.5 NIC.
> I added a static route of 0.0.0.0 mask 0.0.0.0 192.168.9.1
> From the server itself, I can ping the remote network with this setup.
> That's good.
>
> If I try to vpn into the box using our external IP, (port forwarded to
> this
> box using the Linksys router) I am unable to connect.
>
> If I disable the interface, then I can vpn in with no problems. That then
> allows me to RDC to the desktop, ENAB:LE the interface and then I'm able
> to
> work on the remote network.
>
> It still seems like I've either incorrectly setup the static route or I
> need
> an additional route...or something.??
>
>
>
>
>
>
> "Todd J Heron" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Does the internal NIC have a default gateway defined? If it does, remove
>> that. Next, you will need to setup a static route to reach your internal
>> network from the RRAS server.
>>
>> --
>> Todd J Heron, MCSE
>> Windows Server 2003/2000/NT; CCA
>> --------------------------------------------------------------------------
> --
>> This posting is provided "as is" with no warranties and confers no rights
>>
>
>

"Mark Rodgers" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Thanks for the reply Todd.
>
> I erased the gateway from the 192.168.9.5 NIC.
> I added a static route of 0.0.0.0 mask 0.0.0.0 192.168.9.1

That is not a Static Route,...that is a Default Gateway Route. Get rid of
it.

Better yet,...from the command prompt type "Route /f" and rebot. If the
Nics are configured correctly the Table will be rebuilt correctly, then
leave it alone. I see no reason for you to ever manually touch the Route
Table in this situation.

> If I try to vpn into the box using our external IP, (port forwarded to
this
> box using the Linksys router) I am unable to connect.

Compare your RRAS setup to these articles,...use the right one for your OS
version.

Virtual Private Networking with Windows 2000: Deploying Remote Access VPNs
http://www.microsoft.com/windows2000.../vpndeploy.asp

Microsoft Windows Server 2003 Remote Access/VPN Server Role
http://www.microsoft.com/technet/pro...94b01f615.mspx

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com