Re: Test Networks Can't See Internet
- From: Nordic <nospam@xxxxxxxxxx>
- Date: Wed, 18 Jan 2006 23:42:32 -0800
Thanks, Bill. That is what I thought too. But, I added a static route for
192.168.200.0 and it still fails. The route table from the Linksys is below:
Destination LAN IP Subnet Mask Gateway Interface
<publicIP> 255.255.255.248 0.0.0.0 WAN
(Internet)
192.168.200.0 255.255.255.0 192.168.90.6 LAN & Wireless
192.168.90.0 255.255.255.0 0.0.0.0 LAN & Wireless
0.0.0.0 0.0.0.0 <publicIP> WAN
(Internet)
Do I have that right? Any other thoughts?
"Bill Grant" <not.available@online> wrote:
> To get to the A and B sites from the production LAN (and the
>Internet) you will need extra static routes on the Linksys router. Its
>default route is out to the Internet, so it will not automatically route
>traffic for the 192.168.20x subnets to the RRAS routers. You will need to do
>that yourself. eg
>
>192.168.200.0 255.255.255.0 192.168.90.6
>192.168.210.0 255.255.255.0 192.168.90.5
>
> That should get it working. Traffic to the Internet from A and B will go
>first to the RRAS routers then to the Linksys (both by default routing). On
>the return journey, the Linksys will forward traffic for the 192.168.20x
>subnets to the appropriate RRAS router, which can deliver directly.
>
.
- Follow-Ups:
- Re: Test Networks Can't See Internet
- From: Bill Grant
- Re: Test Networks Can't See Internet
- References:
- Test Networks Can't See Internet
- From: Nordic
- Re: Test Networks Can't See Internet
- From: Bill Grant
- Test Networks Can't See Internet
- Prev by Date: Configuring AD between to Remote sites with NAT on both sides
- Next by Date: Re: RRAS clients not updating WINS / DNS
- Previous by thread: Re: Test Networks Can't See Internet
- Next by thread: Re: Test Networks Can't See Internet
- Index(es):
Relevant Pages
|
Loading