Routing between two LANs using RRAS

[Mike M.]

I'd appreciate your help for the following scenario: two networks,
194.31.199.x and 172.16.x.x, shall be connected for some months. Therefore,
a windows 2000 server was installed, which connects to both networks using
two NICs (194.31.199.240, 172.16.11.3). Routing was enabled using RRAS with
the assistant for "lan-connection router". IPX routing just works fine, but
IP routing does not.

The routing server itself can ping the clients in both networks. But, a
client e.g. in the 172 net, on which the route command was used (route -p
add 194.31.199.0 mask 255.255.255.0 172.16.11.3), can only ping the IPs of
both server NICs, but not clients in the network behind the router.

"netsh routing ip show rtmroutes" on the W2K server shows (only
LAN-connections listed):

172.16.0.0/16 - Local - 1 - 1 - Gw 172.16.11.3 - Vw. UM - LAN-Connection 2

194.31.199.240/32 - Local - 1 - 1 - Gw 194.31.199.240 - UM - LAN-Connection

224.0.0.0/4 - Local - 1 - 1 - Gw 172.16.11.3 - U - LAN-Connection 2

224.0.0.0/4 - Local - 1 - 1 - Gw 194.31.199.240 - U - LAN-Connection

255.255.255.255/32 - Local - 1 - 1 - Gw. 172.16.11.3 - U - LAN-Connection 2

255.255.255.255/32 - Local - 1 - 1 - Gw. 194.31.199.240 - U - LAN-Connection

Also tried changing registry setting
HKLM\system\CCS\Services\tcpip\Parameters\IPEnableRouter to "1", without any
effect.

So, what's going wrong, what did I miss?

Thanks in advance.

 

[Tom Turck]

Mikey,

What is the default gateway of the remote clients? For
your ping test to work as described the gateway of the
194.31.199.0/24 network must be 194.31.199.240. You can
test this by adding a static route on a single remote host
on the 194.31.199.0 network: route add 172.16.0.0
255.255.0.0 194.31.199.240

Since the ping is a round trip the default gateway of both
networks must know the next hop to the destination network.
The ping test on the router itself works because the
networks are directly attched.

Another thing worth mentioning is that 194.31.199.0 is a
part of a large public IP address block leased by RIPE.net
and you may have issues routing combining ip addresses in
the public range and the private ip range.

 

[Mike M.]

Yes, you are completely right... it's a round trip. In my configuration, it
was a "trip without return", I guess... - I totally oversaw that the targed
machine had an outdated gateway entry *blush*.

Thanks for helping out someone who forgot thinking before asking

Mike