Re: Routing behind NAT server
From: Phillip Windell (_at_.)
Date: 12/29/04
- Next message: Steve Riley [MSFT]: "Re: blocking internet access"
- Previous message: Dusko Savatovic: "Re: Client's Bandwidth"
- In reply to: ping: "Re: Routing behind NAT server"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Dec 2004 10:21:51 -0600
"ping" <wterng@gmail.com> wrote in message
news:1104334133.828134.196360@z14g2000cwz.googlegroups.com...
> Could it be the NAT(of modem) filters out the packet as it is not
> originate from 1.1 network(assign by DHCP.)?
>
> Yes, I have set RIP on both modem and win2k server. The internal
> network routing is fine. Only the 3.x network refuses to go to
> internet.
I suspect that RIP isn't really working on the NAT Device, so the NAT device
has no idea where 192.168.3.x is or how to get there. I don't know why you
are even trying to bother with it anyway. The only thing you need is one
single static route on the NAT Device that specifies that the route to
192.168.3.x is found by using the gateway of 192.168.1.13 from the interface
192.168.1.1.
None of the other machines need any "routes" at all.
The hosts (except the Server) on 192.168.3.x will all use 192.168.3.254
(Server internal Nic) as their Default Gateway.
The hosts (except the Server) on 192.168.1.x will use192.168.1.13 (Server
external Nic) as their Default Gateway.
The Server will *only* use 192.168.1.1 (NAT Device) as the Default Gateway.
This will exist *only* on the External Nic (192.168.1.13). The internal Nic
will have a *blank* Default Gateway.
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com
- Next message: Steve Riley [MSFT]: "Re: blocking internet access"
- Previous message: Dusko Savatovic: "Re: Client's Bandwidth"
- In reply to: ping: "Re: Routing behind NAT server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
