Re: 2 Nics...1 Problem

From: Matthew [MSFT] (mfresoli_at_online.microsoft.com)
Date: 04/08/04 

Date: Thu, 8 Apr 2004 14:55:06 -0400

Hi John,

>From the information it sounds like you have a firewall connected via
192.16.10.x/24 network to your gateway server. Then the gateway server has
another network 192.16.20.x/24. From the route print on the gateway
server, it looks like there are 2 default gateways set (one on each nic).
The 192.16.10.99 NIC is the only one that should have a default gateway.
(although this is probably not the issue, if this is correct, I would remove
the extra default gateway).

Also, you should not have to place any static routes on the gateway server
since its route table already has both networks listed. I dont see the
routes in the route table, so I am not sure if these are being used. (if
they are there, I would remove these as well).

Since your firewall has the route back to the gateway server for
192.16.20.x/24, then it should take any packets from the clients routed to
the default gateway (assume it is 192.16.10.102), then it should route the
packets back.

To make sure you dont have an issue with the firewall routing packets back,
I would suggest taking a machine in the 192.16.10.x network and point the
default gateway back to 192.16.10.99 (or place a static route on a client to
point back for 192.16.20.x). Then ping from a machine in the 192.16.20.x
network and see if the packet is returned.

If it is, then there may be an issue with the firewall route. If this
fails, I would suggest a tracert or pathping command to see if they return
more information.

Hope this helps.

-Matt 

-- 
[This posting is provided AS IS
with no warranties, and confers
no rights.]
"John McKee" <Destroyer24@hotmail.com> wrote in message
news:6d13dce0.0404080957.183b606@posting.google.com...
> I have a multi-homed system connected to 2 different networks. I also
> have a another gateway running as a nat/firewall to the outside.
>
> The gateway has 2 nics...old network is at 192.16.10.99 and the new
> network is at 192.16.20.99. The firewalled machine has 2 nics as
> well...192.16.10.102 and the other nic is the outside ip.
>
> One computer (gateway) is connected to 2 different networks,
> 192.16.20.x and 192.16.10.x I tried to config this one as a router
> between the two networks. However, when I try to ping from one network
> to the other...it doesnt work. Im only able to ping the nics on the
> gateway from the firewalled machine. If I try any other machine on the
> 10.x network it pings once...then it RTOs. After that it doesnt ping
> again.
>
> In my static routes for the gateway I have 10.99 goto the 20.99 and
> 20.99 goto the 10.99
>
> Active Routes:
> Network Destination        Netmask          Gateway       Interface
> Metric
>           0.0.0.0          0.0.0.0    192.16.10.102     192.16.10.99
>   20
>           0.0.0.0          0.0.0.0    192.16.20.220     192.16.20.99
>   20
>         127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1
>    1
>       192.16.10.0    255.255.255.0     192.16.10.99     192.16.10.99
>   20
>      192.16.10.99  255.255.255.255        127.0.0.1        127.0.0.1
>   20
>       192.16.20.0    255.255.255.0     192.16.20.99     192.16.20.99
>   20
>      192.16.20.99  255.255.255.255        127.0.0.1        127.0.0.1
>   20
>    192.16.255.255  255.255.255.255     192.16.10.99     192.16.10.99
>   20
>    192.16.255.255  255.255.255.255     192.16.20.99     192.16.20.99
>   20
>         224.0.0.0        240.0.0.0     192.16.10.99     192.16.10.99
>   20
>         224.0.0.0        240.0.0.0     192.16.20.99     192.16.20.99
>   20
>   255.255.255.255  255.255.255.255     192.16.10.99     192.16.10.99
>    1
>   255.255.255.255  255.255.255.255     192.16.20.99     192.16.20.99
>    1
> Default Gateway:     192.16.10.102
>
> In the staic routes on the firewall I have anything going to the 20.x
> goto the 10.99
>
> Please help me.
>
> --John

Relevant Pages

  • Re: [SLE] connection redundancy
    ... which is the router just this side of the ... >>because it's own gateway is still up. ... You'll also need three network cards to put into this Linux box. ... your internal LAN can route packets to the Internet. ...
    (SuSE)
  • Re: One computer on 2 networks
    ... The gateway setting on the 172.30 NIC should be blank. ... If they are not all 172.30 you need to use a shorter network mask (so ... How exactly would the Route Add sentence be? ... and yours must point to the Internet gateway. ...
    (microsoft.public.windows.server.networking)
  • Re: connecting two private subnets
    ... pre-existing network and visaversa. ... OK - but they aren't on the same wire, and you need to have a gateway ... could be "if no other route goes where you want, ... (Gotta love it - 16.777 millions hosts on the same wire. ...
    (comp.os.linux.networking)
  • Re: Routing a Dial-in Router ...
    ... > of ip addresses on the same subnet as the server. ... should end up with a host route and you just need to add the network route ... If the gateway has a suitable OS, ...
    (comp.os.linux.networking)
  • Re: 2 Nics...1 Problem
    ... > From the information it sounds like you have a firewall connected via ... > 192.16.10.x/24 network to your gateway server. ... > since its route table already has both networks listed. ...
    (microsoft.public.windows.server.networking)