grrr...W2K Server routing...grrr

[Mark R]

I'm configuring a test environment with two domains each
behind their own W2K Server router. Here is my basic
topology:

10.10.10.10 Server 1
|
10.10.10.1 private NIC of W2K RRAS 1
|
192.168.1.1 public NIC of W2K RRAS 1
|
192.168.1.2 public NIC of W2K RRAS 2
|
10.10.20.1 private NIC of W2K RRRAS 2
|
10.10.20.10 Server 2

With RRAS configured (basic) Server 1 and 2 can see to the
private side of the opposite RRAS server, but no further.
I've tried static routes, DOD connections VPN, etc., etc.
I thought I was a decent routing/switching person (with
the right equipment...Ci*co) but I absolutely cannot figure
this out. The IP route tables on each of the RRAS servers
seem overly large and unnecessary considering the small
amount of topology we are dealing with. Lemme know if W2K
Server can handle this or if I should put a tried and true
enterprise-class routing solution in place...

Sorry for the jib at MS, but it's been a LLLOOONNNGGG day
with this...

Mark

 

[Mark R.]

Sorry for the post! I finally got it together, looked more
closely at my (inadequate) subnetting and fixed my
mistake. My apologies to MS and the group!

Mark