Re: 2 Nics...1 Problem

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: John McKee (Destroyer24_at_hotmail.com)
Date: 04/11/04

  • Next message: Herb Martin: "Re: Adding Global Groups to Local" 
    Date: 11 Apr 2004 16:04:13 -0700

    Actually it did help :)

    After some testing though I came up with the easiest solution. I
    connected the 2 networks together (coupler) and now everything works
    fine.

    Thanks for your help :)

    --John

    "Matthew [MSFT]" <mfresoli@online.microsoft.com> wrote in message news:<uyX9FsZHEHA.4088@TK2MSFTNGP10.phx.gbl>...
    > 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

  • Next message: Herb Martin: "Re: Adding Global Groups to Local"

    Relevant Pages

    • Re: Urgent RRAS wont work Help!
      ... Where you need the extra routing is on the firewall. ... route but whatever config I use it won't route. ... The clients on the ... network have the default gateway set as 184.155.0.80 via DHCP. ...
      (microsoft.public.win2000.ras_routing)
    • Re: Lost Internet Access
      ... Then you *do* have a network connectivity problem... ... the box should have a default route pointing towards your ... Firewall: if the firewall is blocking traffic similar symptoms would ... Was nscd removed recently? ...
      (Debian-User)
    • Re: Urgent RRAS wont work Help!
      ... plus it worked before without a route on the FW. ... > Where you need the extra routing is on the firewall. ... > port access rights to clients on the 184.155.0.0 network. ...
      (microsoft.public.win2000.ras_routing)
    • Re: [fw-wiz] An interesting VPN problem
      ... > (including the traffic that should ultimately end up on the Internet). ... > Traffic from the remote network not targeted for the local network ... > should be routed through a firewall reachable from the local network. ... Host route for external IP address of L-PIX directed to "the Internet" ...
      (Firewall-Wizards)
    • Re: Source 126.0.0.1 UDP/137
      ... The reason you're seeing it on the firewall is ... the internet since you don't have a route for this network. ... > that are enforced to protect WLANs from known vulnerabilities and threats. ...
      (Incidents)