RRAS Issue -Dual NIC's

We're having an issue with a 2K3 Server setup for RRAS.

The machine has two NIC's: 192.168.2.x (WAN) and 10.0.0.x (LAN)

The server provides VPN connections over 192.x network and gives clients
access to the 10.x local machines....shared folders...etc.

The server also provides dial-up access through modems so stranded clients
can get on over phone lines and use local resources as well as get access to
the internet. They also get assigned to that 10.x network.

The problem is with the gateway configuration. If the WAN side NIC has a
gateway listed in it's config, VPN clients can connect over the internet and
dial-up clients can hit the LAN machines, but dial-up clients can't browse
out to the public internet (no gateway listed on that NIC).

If we list a gateway on the LAN side (10.x), dial-up clients can connect
locally and browse the internet, but VPN clients get an "800" error and the
server refuses to respond. Listing multiple gateway (one in each NIC) does
not solve the issue either...VPN members still get the 800 error until the
gateway is removed from the LAN.

How can this be resolved without simplifying the server to one NIC? There
must be a way to tell the server if traffic is requested for a network
outside 10.x, forward it to the 192.x gateway.....correct?

Thanks for your help!

Have you enabled IP routing? post the result of ipconfig /all may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"eleska" <(E-Mail Removed)> wrote in message news:3622772C-AC1D-4478-B566-(E-Mail Removed)...
We're having an issue with a 2K3 Server setup for RRAS.

The machine has two NIC's: 192.168.2.x (WAN) and 10.0.0.x (LAN)

The server provides VPN connections over 192.x network and gives clients
access to the 10.x local machines....shared folders...etc.

The server also provides dial-up access through modems so stranded clients
can get on over phone lines and use local resources as well as get access to
the internet. They also get assigned to that 10.x network.

The problem is with the gateway configuration. If the WAN side NIC has a
gateway listed in it's config, VPN clients can connect over the internet and
dial-up clients can hit the LAN machines, but dial-up clients can't browse
out to the public internet (no gateway listed on that NIC).

If we list a gateway on the LAN side (10.x), dial-up clients can connect
locally and browse the internet, but VPN clients get an "800" error and the
server refuses to respond. Listing multiple gateway (one in each NIC) does
not solve the issue either...VPN members still get the 800 error until the
gateway is removed from the LAN.

How can this be resolved without simplifying the server to one NIC? There
must be a way to tell the server if traffic is requested for a network
outside 10.x, forward it to the 192.x gateway.....correct?

Thanks for your help!