Re: RRAS doesn't R

Did you run route add on the server or the client? It should work on the
client - don't think you need the metric. However, the SQL servers also
need a route to 192.168.0.x - probably they are sending replies to
192.168.1.2 instead of 192.168.1.254.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Briscobar" <youcant@xxxxxxxxxxxxxx> wrote in message
news:#j36$It7GHA.4996@xxxxxxxxxxxxxxxxxxxxxxx
Hello all,

Let me give you a little background here:

A remote user now needs access to our network. She needs to connect via
VPN
and have DNS work, basically. She needs to run a couple programs that
require network connectivity, since they access SQL servers located here
on
our network. So here's what I did.

Our office is only one subnet. 192.168.1.x. It runs fine and everyone's
happy. The thing is, I want the VPN users to be logically separated from
our
network. So I threw a new NIC into the VPN-server-to-be and put that NIC
on
its own subnet (192.168.0.x).

For reference, the VPN-server-to-be has 2 IP addresses: 192.168.1.254
(same
subnet as the rest of our network)
192.168.0.29 (this is for the VPN subnet)

Then I installed RRAS. Yay! It installed! I gave the appropriate users
permissions to dial in. I forwarded ports on the firewall. I connected to
the VPN from my machine here at work, so I know that I can dial in. I
connected to my machine from home, so I know the router is forwarding
ports.
The "RAS" part of RRAS is working fine. It's the first R that I'm having
trouble with.

When I dial in, I'm assigned an IP address on the 192.168.0.x subnet.
Great.
From the VPN client, I can ping the VPN server at 192.168.0.29. Yay!
Connectivity! But that's as far as I can go. It's the routing between the
192.168.0.x and 192.168.1.x subnets that has my panties in a twist.

Maybe I'm an idiot and don't know how to use static routes. Maybe the darn
thing just doesn't work. I don't know, and frankly I don't care, as long
as
I can get it to work. I've spent 2 days on this thing, and all my VPN
clients can do is access the VPN server. They can't access other network
resources, by IP or by name (obviously, since routing isn't getting done
at
all between the subnets).

Again, here's my setup:

Dataman (my VPN Server)
NIC1:
IP: 192.168.1.254
SM: 255.255.255.0
DG: 192.168.1.2
DNS: 192.168.1.5

NIC2:
IP: 192.168.0.29
SM: 255.255.255.0
DG: (none)
DNS: 192.168.1.5

VPN Clients get an IP on the 192.168.0.x subnet.

Here's the routing table from a "route print" done on Dataman, the VPN
server:

IPv4 Route Table

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x10003 ...00 60 67 30 ae cb ...... Intel 21140-Based PCI Fast Ethernet
Adapter
(Generic)
0x10004 ...00 17 31 c3 d5 f4 ...... Marvell Yukon 88E8053 PCI-E Gigabit
Ethernet
Controller

===========================================================================

===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.2 192.168.1.254
10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.29 192.168.0.29
20
192.168.0.2 255.255.255.255 192.168.0.11 192.168.0.11
1
192.168.0.11 255.255.255.255 127.0.0.1 127.0.0.1
50
192.168.0.29 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.0.255 255.255.255.255 192.168.0.29 192.168.0.29
20
192.168.1.0 255.255.255.0 192.168.1.254 192.168.1.254
1
192.168.1.254 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.254 192.168.1.254
1
224.0.0.0 240.0.0.0 192.168.0.29 192.168.0.29
20
224.0.0.0 240.0.0.0 192.168.1.254 192.168.1.254
1
255.255.255.255 255.255.255.255 192.168.0.29 192.168.0.29
1
255.255.255.255 255.255.255.255 192.168.1.254 192.168.1.254
1
Default Gateway: 192.168.1.2

===========================================================================
Persistent Routes:
None


Anyone? Slightest hint as to how I can route between the two networks? I
feel like a total doofus. I tried a "route add", but it didn't seem to
work.
I tried "route add 192.168.1.0 mask 255.255.255.0 192.168.0.29 metric 3 IF
3" but that didn't work. What I expect that route print to do is add a
route
for all traffic to the 192.168.1.0 subnet from the 192.168.0.0 subnet, via
the gateway 192.168.0.29 (which is the VPN server itself). But that's a no
go. Am I wrong in trying that?

I've googled, technetted, tried every combination I could think of. And
nothing. This VPN sh1t is for the birds, I'll tell you that.

Break it down for me like I'm an idiot, which I am. Thanks.

Ken





.

Relevant Pages

  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with connectcomputer and active directory
    ... I understand that you would like to join a remote client to the domain. ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ... Create a VPN connection to ISA/RRAS on the Internet ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • RE: Route added by RRAS that overrides local LAN route on NIC
    ... I am using SBS as the VPN server. ... The route I am speaking of is the route to local LAN that is put in the ... After the RAS client connects there is another route added so the two ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... Are you saying that an XP Home PC wouldn't be able to connect to a server share over VPN? ... Can ping the SBS but not the client PCs on the same network. ... gateway matches the IP of the remote client, ...
    (microsoft.public.windows.server.sbs)
Loading