Re: Connecting 2 seperate subnets - 2 NICS

You may not be able to sort this out without the cooperation of the
other party. Routing is a two-way process. It will only work if the remote
site knows how to reach your local subnet as well. Your router needs to know
that it can get to 192.168.0.0 via the Cisco router. But the router at the
other end must also know that it can reach 10.1.0.0/24 through the Cisco
link. Routing will fail if the remote site doesn't how to reach your subnet
(unless you use NAT).

As far as your 10.1 subnet is concerned, I would leave the default
gateway set to the cable router, since this is where most traffic will go.
To get traffic for 192.168 to the RRAS router, add a static route to this
gateway router to "bounce" the 192.168. traffic to your RRAS router. If they
are using a 16-bit subnet mask, this route would be

192.168.0.0 255.255.0.0 10.1.0.15

So the setup at your end would be

Internet
|
cable router (static route 192.168.0.0 255.255.0.0 10.1.0.15)
10.1.0.1
|
client machines
10.1.0.x dg 10.1.0.1
|
10.1.0.15 dg 10.1.0.1
RRAS
192.168.3.20 dg blank
( static route 192.168.0.0 255.255.0.0 192.168.3.25)

This will work as long as the machine you want to connect to in the
192.168. has enough routing info to get replies back through the Ciscos to
your RRAS router. If it doesn't, you will need to get the sysadmin of the
other site to set up the routing. If you can't do this, you will need to
enable NAT on the RRAS server (so that all traffic going to the 192.168
subnet uses the RRAS router's 192.168.3.20 address).

returnoftheyeti@xxxxxxx wrote:
> Here is my setup.
>
> Server2k3 (Domain Controller) - 1st NIC 10.1.0.15 mask 255.255.255.0
> GW 10.1.0.1. 10.1.0.1 is a firewall connected to a cable modem. All
> clients are in the 10.1.0.x subnet and have a mask of 255.255.255.0
> and GW of 10.1.0.15. The other NIC has the IP of 192.168.3.20 with
> a mask of 255.255.0.0 GW 192.168.3.25. 192.168.3.25 is a cisco router
> connected to a T1. T1 is connected to another Cisco at another
> location.
>
> I need to have my clients in the 10.1.0.x subnet access file shares on
> a server whos IP is 192.168.1.1. I have set up RRAS as a LAN router.
> My 2k3 server can ping and browse the server at 192.168.1.1. My
> clients can ping 192.168.3.20, but cannot ping 192.168.3.25 or
> 192.168.1.1
>
> Do I need to add a route to the Cisco?
>
> Is RRAS set up wrong?
>
> Here is a screen shot of my RRAS
> http://edtech.mcc.edu/~janderson4/route.JPG
>
> Thanx for the help


.

Relevant Pages

  • Re: Routing and RRAS Problem - Pleasehelp
    ... Interface List ... but the problem is the PC's on the subnet 1 cannot access the Internet. ... router that is running a DHCP, The IP of the router is ... enable RRAS, and is running fine, Interface called INTERNET is connected to ...
    (microsoft.public.windows.server.networking)
  • Re: Routing and RRAS Problem - Pleasehelp
    ... use RRAS but if will fail I will run RRAS server as NAT Router, ... Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net ... Traffic from your "internal" subnet can get ... You need to add an extra route to the Linksys router so that it knows how to ...
    (microsoft.public.windows.server.networking)
  • Re: Routing and RRAS Problem - Pleasehelp
    ... Traffic from your "internal" subnet can get ... out to the Internet by default routing, but the return traffic will fail. ... You need to add an extra route to the Linksys router so that it knows how to ...
    (microsoft.public.windows.server.networking)
  • Re: Win2k3 LAN Routing Questions
    ... all you need to do is enable IP routing on the router. ... If there was no other network involved, you simply make the router the ... pretty straight forward as long as you can add a route to your NAT router. ... This is important because this router needs to know where your new subnet is ...
    (microsoft.public.windows.server.networking)
  • Re: please advise - problem with routing
    ... > Sorry for the confusion, again, ther is cisco router which connects ... > "Dana Brash" wrote in message ... >> This configuration can be accomplished by changing the subnet mask on ... >> routing anything and just using a different subnet mask, ...
    (microsoft.public.windows.server.networking)
Loading