Windows 2000 Server router setup

[Guest]

Scenario: Currently have one subnet 192.168.1.0 with Linksys broadband
router 192.168.1.1 and a Windows 2000 domain controller/DHCP server/DNS
server/file server/Exchange server 192.168.1.2 and another dedicated Windows
2000 file server 192.168.1.3.

I have installed a second NIC in the 192.168.1.3 server and gave it an IP
address of 192.168.2.1, connected it to a separate switch, and used the
wizard to configure the server as a Network Router.

No other subnets on the network.

Goal: Create a second subnet using Windows 2000 server Router to isolate
the traffic on both subnets, move some users from the 192.168.1.0 subnet to
the 192.168.2.0 subnet, and allow the moved users to still access resources
in the 192.168.1.0 subnet (shares, printers, Exchange mailboxes, etc.) and
allow users in the 192.168.1.0 to access resources in the 192.168.2.0 subnet.

Question: Do I need to configure a static route to let the 192.168.1.0
network know about the 192.168.2.0 network and another static route to let
the 192.168.2.0 network to know about the 192.168.1.0 network? If so, what
is the proper configuration for each of the interfaces? For the 192.168.1.2
interface, is the Destination 192.168.2.0 Netmask 255.255.255.0 Gateway
192.168.1.2 and for the 192.168.2.1 interface, is the Destination 192.168.1.0
Netmask 255.255.255.0 Gateway 192.168.2.1?

It seems that whether or not I configure static routes, I can ping the both
NICs in the server (192.168.2.1 and 192.168.1.3) but no other hosts by IP
address on the 192.168.1.0 subnet from a workstation on the 192.168.2.0
subnet with a DHCP assigned address of 192.168.2.10 255.255.255.0 and default
gateway of 192.168.2.1. What am I missing?

Thanks!

 

[Enkidu]

Scenario: Currently have one subnet 192.168.1.0 with Linksys broadband
router 192.168.1.1 and a Windows 2000 domain controller/DHCP server/DNS
server/file server/Exchange server 192.168.1.2 and another dedicated Windows
2000 file server 192.168.1.3.

I have installed a second NIC in the 192.168.1.3 server and gave it an IP
address of 192.168.2.1, connected it to a separate switch, and used the
wizard to configure the server as a Network Router.

I would purchase a $200 - $300 router to connect your two subnets.
There are many pitfalls in having a DC multi-homed. With all those
other services on there as well you are probably going to have many
headaches, routing being the least of them.

Basically on the 192.168.2.0 subnet all devices NOT on that subnet are
behind 192.168.2.1 so making that the gateway device in all clients
will solve that problem. On the 192.168.1.0 subnet you will need a
static route for the 192.168.2.0 subnet via 192.168.1.3 in all the
*clients*. You shouldn't need a route on the gateway/DC/DHCP/DNS/file
server/Exchange box.

Please consider buying a small router rather than using the one box
for everything!

Cheers,

Cliff