Connect 2 LANs via 2 NICs - Windows2000 Server

  • Thread starter Thread starter Bob Brislin
  • Start date Start date
B

Bob Brislin

I have a Windows 2000 server with 2 NICs in it. Each NIC
connects to a different LAN:
LAN1 = 10.1.1.6 / 255.255.255.0
No Default Gateway Defined
LAN2 = 10.22.64.2 / 255.255.255.0
Default Gateway = 10.22.64.1

The Windows 2000 server can access and ping all computers
on each network.

My goal is to get a computer on the 10.22.64.0 network to
access a computer on the 10.1.1.X network. Specifically,
10.22.64.242 needs to access a share on 10.1.1.13.

I have activated RRAS on the Win2K server and selected to
use it as a router.

From 10.22.64.242, I could not ping 10.1.1.6 until I keyed
in the following from CMD prompt:
route -p add 10.1.1.0 mask 255.255.255.0 10.22.64.2

Now I can ping 10.1.1.6 but cannot ping any other computer
on the 10.1.1.0 network.

Also, on the Win2K server in the registry I changed the
following key to 1:
HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\IPE
nableRouter

What do I need to do to connect these two LANs?? It sounds
simple (and Im sure it is), but I've been fighting with
this all day.

Thanks,
Bob Brislin
(e-mail address removed)
 
The clients on LAN1 and LAN2 need a way to route to each other. If there are
no other routers and networks involved all you need to do is assign the
correct default gateway to the clients:

LAN1 client DG = 10.1.1.6
LAN2 client DG = 10.22.64.2

If your clients already have default gateways (an need them) you don't want
to change the DGs, but instead add routes on the routers being used as the
clients DGs.

Router on LAN1 will need a route to the 10.22.64.x subnet using 10.1.1.6 as
a gateway
Router on LAN2 will need a router to the 10.1.1.x subnet using 10.22.64.2
as a gateway



--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
That's how IP routing works. There must be a route to get the data to the
router. Presumably the default route of the clients is not to your RRAS
router.

If you want this to work for all clients, add the route to the default
router. Otherwise you will need to add it to every client machine you want
to "see".
 
Thanks guys --
Bill: Since I don't have access to the Default Gateway
(10.22.64.1 in this case), What do I need to add to every
client machine I want to see?
I only have 1 computer (10.22.64.242) that needs to
access 10.1.1.13. It looks like you are saying that I CAN
do it through the Win2K Server (10.22.64.2 & 10.1.1.6).
 
Why didn't this CMD:
route -p add 10.1.1.0 mask 255.255.255.0 10.22.64.2
entered at computer 10.22.64.242 give it access to
everything on the 10.1.1.0 network? It only allowed it to
access 10.1.1.6 (NIC 2 in the Win2K Server)??
 
Back
Top