Re: RRAS problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Routing is a two-way process, so there are really two things you need to
check. The machines in 192.168.0.0 need to know how to reach 192.168.2.0 .
But more importantly the machines in 192.168.2.0 need to know how to reach
192.168.0.0 ! If it is across a VPN tunnel, then they must send the traffic
for 192.168.0.0 through the tunnel to 192.168.1.0 first.

So the clients in 192.168.0.0 must send traffic for both 192.168.1.0 and
192.168.2.0 to the RRAS router (to prevent it going to the Internet
gateway). Then the RRAS router must forward traffic for 192.168.2.0 across
the VPN link (to prevent it going to that subnet's Internet router by
default). This is the bit you have done.

At the other end, clients in 192.168.2.0 must send traffic for both
192.168.0.0 and 192.168.1.0 through the VPN tunnel. Then the tunnel endpoint
router must forward traffic for 192.168.0.0 to the RRAS router.

msnews.microsoft.com wrote:
> There are three subnets
>
> 192.168.0.xxx
> 192.168.1.xxx
> 192.168.2.xxx
>
> All three subnets have separate connections to the Internet through
> their gateways
> 192.168.0.1
> 192.168.1.1
> 192.168.2.1
>
> There is a VPN tunnel from 192.168.1.1 to 192.168.2.1
> There is a server that is multi-homed (two network cards) at
> 192.168.1.6 and 192.168.0.6
> This server has RRAS working and is successfully routing traffic
> between 0.xxx and 1.xxx
>
> I would like traffic from 2.xxx to be able to get to 0.xxx by going
> through 1.6 and 0.6
>
> Does this help? I'm not sure how to draw a diagram suitable in a text
> message.
> regards,
> mark
>
>
> "Sharoon Shetty K [MSFT]" <sharoons@xxxxxxxxxxxxxxxxxxxx> wrote in
> message news:u3KO5UycFHA.2076@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi,
>> Can you post a simple network diagram to understand the setup
>> better? Also, specifically, its not clear where the machine
>> 192.168.0.1 is located in the network?
>>
>> --
>> Thanks,
>> Sharoon
>> ---------------------------------------------------------
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "msnews.microsoft.com" <john@xxxxx> wrote in message
>> news:OTEUNKvcFHA.3880@xxxxxxxxxxxxxxxxxxxxxxx
>>> I would like to get RRAS working on a win 2k server with two network
>>> cards.
>>>
>>> I have two subnets
>>> 192.168.0.xxx
>>> 192.168.1.xxx
>>>
>>> The win2k server has IP
>>> 192.168.0.6
>>> 192.168.1.6
>>>
>>> I can see all the machines on 0.xxx from 1.xxx
>>> I can see all the machines on 1.xxx from 0.xxx
>>>
>>> I need to be able to route to 2.xxx which goes through 192.168.1.1
>>> I can see 192.168.1.6 from all of 2.xxx
>>>
>>> On the gateway 192.168.0.1 I have a route to send 2.xxx to
>>> 192.168.0.6 I have a routing table on the win2k server
>>>
>>>
>>> IPv4 Route Table
>>> ===========================================================================
>>> Interface List
>>> 0x1 ........................... MS TCP Loopback interface
>>> 0x10003 ...00 02 b3 0b 35 18 ...... Intel(R) PRO/100+ Management
>>> Adapter 0x10004 ...00 d0 b7 85 37 5c ...... Intel(R) PRO/100+
>>> Management Adapter #2
>>> ===========================================================================
>>> ===========================================================================
>>> Active Routes:
>>> Network Destination Netmask Gateway Interface
>>> Metric
>>> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.6
>>> 1
>>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>>> 1
>>> 192.168.0.0 255.255.255.0 192.168.0.6 192.168.0.6
>>> 20
>>> 192.168.0.6 255.255.255.255 127.0.0.1 127.0.0.1
>>> 20
>>> 192.168.0.255 255.255.255.255 192.168.0.6 192.168.0.6
>>> 20
>>> 192.168.1.0 255.255.255.0 192.168.1.6 192.168.1.6
>>> 1
>>> 192.168.1.6 255.255.255.255 127.0.0.1 127.0.0.1
>>> 1
>>> 192.168.1.255 255.255.255.255 192.168.1.6 192.168.1.6
>>> 1
>>> 192.168.2.0 255.255.255.0 192.168.1.1 192.168.1.6
>>> 1
>>> 224.0.0.0 240.0.0.0 192.168.0.6 192.168.0.6
>>> 20
>>> 224.0.0.0 240.0.0.0 192.168.1.6 192.168.1.6
>>> 1
>>> 255.255.255.255 255.255.255.255 192.168.0.6 192.168.0.6
>>> 1
>>> 255.255.255.255 255.255.255.255 192.168.1.6 192.168.1.6
>>> 1
>>> Default Gateway: 192.168.1.1
>>> ===========================================================================
>>> Persistent Routes:
>>> None
>>>
>>> I would like to know why this is not working and if there is an
>>> example of what to do.
>>> thank you
>>> mark


.

Relevant Pages

  • Re: Network Configuration Problem
    ... >> in different geographic locations and connected by a VPN tunnel. ... >> COMPANY.LOCAL has the global active directory server, DNS server, and ... > I believe you need to point the Child DC and Exchange server to the child ...
    (microsoft.public.windows.server.dns)
  • Re: RRAS problem
    ... If it is across a VPN tunnel, ... > and 192.168.2.0 to the RRAS router (to prevent it going to the Internet ... Then the RRAS router must forward traffic for 192.168.2.0 across ... >>> Can you post a simple network diagram to understand the setup ...
    (microsoft.public.win2000.ras_routing)
  • SBS 2003 sudden services problem over router based vpn
    ... on the server end the lan is 10.0.0.x, ... users on remote end have happily used outlook 2003 to establish pop3 ... email via pop3 when accesing the server through the vpn tunnel by it's ...
    (microsoft.public.windows.server.sbs)
  • SBS 2003 sudden authentication prob over router based vpn
    ... on the server end the lan is 10.0.0.x, ... users on remote end have happily used outlook 2003 to establish pop3 ... email via pop3 when accesing the server through the vpn tunnel by it's ...
    (microsoft.public.windows.server.sbs)
  • SBS 2003 sudden authentication prob over router based vpn
    ... on the server end the lan is 10.0.0.x, ... users on remote end have happily used outlook 2003 to establish pop3 ... email via pop3 when accesing the server through the vpn tunnel by it's ...
    (comp.security.firewalls)