Re: Keep routing table

that's it... thanks. I suppose that i can't control the packet... but... in a
configuration a found, every nic reply to their own router...

well... so

Thanks a lot. i proceed with the steps you send me.

Thanks.

Massimo Artini

"Phillip Windell" wrote:

> "Massimo Artini" <MassimoArtini@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4A40E032-955C-4E61-8AF0-B1FFCDFF0C8A@xxxxxxxxxxxxxxxx
>
> > well i use nektwork monitor to view trafic on the 81.75.35.236 NIC and
> > the 62.110.203.202 NIC. So i can see a request on 62.110.203.202 and the
> > reply on 81.75.35.236.
>
> That isn't your problem and is actually not a problem,...it is normal. The
> path taken is not "stateful", only the packets internally are statefull and
> the packets don't care how they got there, only that they got there. In
> otherwords the path taken in the return direction has no relationship to the
> path taken on the outbound side. Each path is determined independently based
> on the routing scheme at the Source. This means you have no control over
> the route taken for the return path, you only control the outbound path.
>
> Your big problem is that you are running 4 nics in the ISA with three
> Default Gateways. Of the three Default Gateways,...2 are done in the GUI and
> one is manually entered in the Routing Table.
>
> You can only have *one* Default Gateway. By the very definition of the
> term, you can only have one. Since the inbound traffic seems to return to
> the 81.75.35.236-237 Interface then that is the one where the Default
> Gateway goes.
>
> All other Interfaces *must* leave the Default Gateway blank. Any "paths"
> you require must be entered into the Routing Table manually and they must be
> *specified* paths,...you can not use "0.0.0.0" as the Destination in the
> route.
>
> 1. Correct the Default Gateway problem in the GUI of the Nics.
> 2. Clear the Route Table by using "Route /f" from a command prompt.
> 3. Reboot the machine to let the Route Table rebuild correctly.
> 4. Enter any required Static Routes into the Routing Table. "0.0.0.0" is
> not allowed in the Static routes you create
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
.

Relevant Pages

  • Re: Multiple external interfaces
    ... you should only need to enter a gateway once for the default ... routing table (unless you are routing to two different gateways, ... Assuming that your default route is set to go out eth0, ... I want to route the traffic from my 10.0.0.x subnet ...
    (comp.os.linux.networking)
  • Re: dialup modem connection
    ... >seems that your default route is not set to your ISP ... the gateway device is not properly set. ... Kernel IP routing table ... Copyright 2005 by Maurice Eugene Heskett, ...
    (Debian-User)
  • Re: Persistent Route ignored on W2K when destination network is unavailable
    ... Although it would seem it should work, the client's routing table is not ... routes it via the static route to the proper gateway. ... > 1 hour the workstations lose connectivity with the remote subnet. ...
    (microsoft.public.win2000.networking)
  • Re: Multihomed Terminal Server
    ... Microsoft MVP - Terminal Server ... Phillip Windell wrote: ... Is it a routing issue, a Gateway issue? ...
    (microsoft.public.windows.terminal_services)
  • Re: ethernet routing
    ... interface but not the 10.20.4.48 interface. ... But you set the default gateway to 10.20.x.x which it can not get to. ... I ususally add a '-host' entry to the routing table. ... 'route add default gw 192.168.1.1' fixes the route on host1 then on the gateway1 machine: 'route add default gw 10.20.4.48' to help packets go to gateway2 if needed. ...
    (Debian-User)