Routing Between 2 Segments of Networks.

[Vikrant]

Hi,
I have 2 networks. 192.168.0.0 and 10.0.0.0 segments.
How do i accompolish routing between the two with a single
windows 2000 server configured as a router.
Want a host in 192 segment to talk to another host in 10
segment.
I am able to ping to the router interface of 192 segment
from my 10 segment host.
Can anyone help in this?
Regards
Vikrant

 

[Sebastjan Kocelj, Avtenta.SI]

Hi, Vikrant

I think you could do that with RIP protocol.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;241545

--
Best Regards,
Sebastjan Kocelj, MCSA
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services

 

[Clark Satter [MSFT]]

In order to do this you will need to have two network adapters in the server, one configured for each subnet. You will then need to configure RRAS on the
server, and finally set the default gateway on the clients for each subnet to the IP of the network adapter on the RRAS server.

So if the server IP address is 192.168.1.1 then clients on the 192.168.x.x segment will point to 192.168.1.1 for their default gateway.

Regards,
Clark Satter
MCSA MCSE A+
Microsoft Networking Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
--------------------

 

[Phillip Windell]

RIP is useless with only one Router and only route to any destination. RIP
is need when there are multiple routers with multiple redundant paths to the
same place. RIP helps decide which of the redundnat paths is the best one to
take.

 

[Phillip Windell]

Use RRAS on the Win2000 box. You want to set it up as a LAN Router,...RRAS
can be setup in several ways, so don't pick the wrong one. The "LAN Router"
is the model you want.

There will be *no* "routes" to configure because both networks are
physically connected to the same router, so the router will automatically
know where they are. The official Cisco term for this is a "Directly
Connected Network" (creative,..eh?) and there are no "routes" required for
this situation. The Clients will use the router as their Default Gateway and
will point to the router nic that directly faces them.

Note that Netbios, Network NeighborHood, and all other "broadcast" based
functionality does not cross routers. So WINS and "Netbios over TCP/IP" is
required for netbios naming and Net'Hood to function properly across two
networks.