Re: Routing Problem

From: Louise Bowman [MSFT] (lbowman_at_online.microsoft.com)
Date: 01/21/05


Date: Fri, 21 Jan 2005 10:02:07 -0800

Kim,

You need to look at the routes on your clients as well.
What default gateways do the clients have?
Your LAN1 Clients have a choice of either setting the default gateway to the
internet gateway router or the LAN1 interface of the server.
If you have the default gateway on LAN 1 Clients to be the IP address of the
internet connection router then that router needs to have a route back to
LAN2.

Clients on LAN 2 need to have a default gateway to the 192.168.200.x
interface on the server.

Thanks

-- 
Louise Bowman
(MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kim" <kmarinelli@nationalticket.com.(don'tspam)> wrote in message
news:C8A1F0AC-998B-47D3-A3C6-590645EA86C2@microsoft.com...
> Lan 1 is using 192.168.200.x mask 255.255.255.0.  Lan 2 is using
> 192.168.100.x snm 255.255.255.0.  These are both on the same segment.
>
> I have a windows 2003 server using 2 nics configured as follows.
> 192.168.200.201 mask 255.255.255.0 with no gateway.  Nic2 192.168.100.224
> mask 255.255.255.0 gateway 192.168.100.254 (out internet
connection/router).
> I have enabled ip routing on the server.
>
> I want lan 1 to be able to see lan 2 and both lans to use the
> 192.168.100.254 internet connection.  My problem is as follows.  when
logged
> onto lan1 I can ping both interfaces on the server but can't ping beyond
that
> to lan 2.  I also can't see anything on lan 2.  My router/internet
connection
> is also configured with the following route 192.168.200.0 255.255.255.0
> 192.168.100.224.  Please see the route print below for the server.  Any
help
> would be appreciated.
>
> Active Routes:
> Network Destination        Netmask          Gateway       Interface
Metric
>           0.0.0.0          0.0.0.0  192.168.100.254  192.168.100.224
20
>         127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1
1
>     192.168.100.0    255.255.255.0  192.168.100.224  192.168.100.224
20
>   192.168.100.224  255.255.255.255        127.0.0.1        127.0.0.1
20
>   192.168.100.255  255.255.255.255  192.168.100.224  192.168.100.224
20
>     192.168.200.0    255.255.255.0  192.168.200.201  192.168.200.201
20
>   192.168.200.201  255.255.255.255        127.0.0.1        127.0.0.1
20
>   192.168.200.255  255.255.255.255  192.168.200.201  192.168.200.201
20
>         224.0.0.0        240.0.0.0  192.168.100.224  192.168.100.224
20
>         224.0.0.0        240.0.0.0  192.168.200.201  192.168.200.201
20
>   255.255.255.255  255.255.255.255  192.168.100.224  192.168.100.224
1
>   255.255.255.255  255.255.255.255  192.168.200.201  192.168.200.201
1
> Default Gateway:   192.168.100.254
>
===========================================================================
> Persistent Routes:
>   None


Relevant Pages

  • Re: Routing Problem
    ... On lan 1 my clients gateway is inferface 192.168.200.201 on the windows ... > internet gateway router or the LAN1 interface of the server. ...
    (microsoft.public.windows.server.networking)
  • Re: Routing to multiple networks behind 2003 PPTP server?
    ... you should use default gateway on remote network. ... I've setup static routes on the PPTP server, but the remote clients ...
    (microsoft.public.win2000.ras_routing)
  • Re: Internal Server
    ... Give the DC no default gateway. ... Use the DC's DNS console ... to enable forwarders and add the router's LAN IP. ... DC for DNS and give the clients a default gateway pointing to the router's ...
    (microsoft.public.windows.server.setup)
  • Re: Internal Server
    ... to enable forwarders and add the router's LAN IP. ... Point all clients to ... DC for DNS and give the clients a default gateway pointing to the router's ... internal and does not have a connection to the internet. ...
    (microsoft.public.windows.server.setup)
  • Re: Supply route to VPN clients
    ... In a LAN-to-LAN VPN you don't do anything with the clients at all. ... Then Your LAN Router's Default Gateway is typically the Firewall leading to ... If you don't have a LAN Router then the VPN Box would be the Client's ...
    (microsoft.public.win2000.ras_routing)