RRAS, Routing, Subnets

[Maxim A.]

We could use some feedback on our RRAS routing situation.

We have 2 DC's in the same domain. Each DC has only 1 NIC and how each
DC is configured is listed below:

DC1
IP: 192.168.0.1
Mask: 255.255.255.0
Gateway: 192.168.0.2

DC2
IP: 192.168.1.1
Mask: 255.255.255.0
Gateway: 192.168.1.2

Now we have a 2k Server configured with 3 NICs and RRAS IP routing.
The first 2 NICs are directly connected to one of the DC's via X-over
cable. The third NIC is connected to a switched network on a different
subnet using a different mask which leads to the Internet. The NICs
are configured as listed below:

NIC to DC1
IP: 192.168.0.2
Mask: 255.255.255.0
Gateway: 134.39.158.132

NIC to DC2
IP: 192.168.1.2
Mask: 255.255.255.0
Gateway: 134.39.158.132

NIC to Switched Network (internet)
IP: 134.39.158.132
Mask: 255.255.255.192
Gateway: 134.39.158.129

Now here is the situation. DC1 and DC2 can ping each other and the
RRAS servers's NIC to the switched network. However DC1 and DC2 cannot
ping the gateway for the Switched Network. The RRAS server itself can
ping everyone including the gateway on the switched network.

What are we doing wrong that is keeping our DC's from being able to
ping the gateway of the switched networks from the DC's? We're trying
to avoid having to hard code any static routes but if thats the only
way it will work, then we will do it. Any advice/observations are
welcome. Thank you!

 

[Bill Grant]

Leave the gateway setting on the LAN NICs of the DCs blank. The only
default route on the RRAS router should be to the gateway in the 134.39.158
subnet.

The gateway router will need to know how to reach the private subnets.
You can achieve this by enabling NAT on the RRAS router. (All traffic to the
gateway will then use the RRAS server's public 134.39 IP address). Configure
the 134.36 interface as public and the two 192.168 interfaces as private.
eg

Internet
|
134.39.158.129
|
134.39.158.132 dg 134.39.158.129
RRAS
|