Re: Persistent Route ignored on W2K when destination network is unavailable

From: Phillip Windell (_at_.)
Date: 07/23/04 

Date: Fri, 23 Jul 2004 08:38:01 -0500

Although it would seem it should work, the client's routing table is not
that place to do this. This should be done at the routing device that they
use (in this case the proxy). Place the static routes on the proxy instead.
Then make sure the full address range of this remote subnet is also included
in the proxy's LAT. The Client's DFG takes them to the proxy box which then
routes it via the static route to the proper gateway. "Routing" (aka IP
Forwarding) must be enabled on the proxy,...which of course isn't the most
desireable thing for a proxy. Proxys should never "double" as a LAN routing
device.

Other questions though, only NAT services require the use of "gateways" to
get to the net,...proxys do not,...proxys use settings in the browser to
"find" the proxy. You may be incorrectly using the proxy as a Default
Gateway. The clients should use a LAN routing device as the Default Gateway
which would itself use the internet gateway as its DFG. Situations vary, and
I have no idea what your situation is. 

-- 
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"ITguy_uk" <itguy_uk@hotmail.com> wrote in message
news:8be6df4c.0407230152.3d7c4fe4@posting.google.com...
> I currently have Windows 2000 Professional (SP4) workstations that
> have persistent routes set to another subnet which is the other side
> of a private WAN connection. These workstations have their default
> gateway set to our internet proxy server which allows them to access
> external sites e.g. web sites and FTP servers. These routes are set
> using:
>
> C:/route -p add <destination IP> MASK 255.255.255.0 <Gateway IP>
>
> e.g:
>
> C:/route -p add <192.168.1.0> MASK 255.255.255.0 <192.168.5.1>
>
> This works as expected as can be seen from tracert (IPs changed to
> example ones):
>
>   Microsoft Windows 2000 [Version 5.00.2195]
>   (C) Copyright 1985-2000 Microsoft Corp.
>
>   C:\>tracert server1
>
>   Tracing route to server1 [192.168.1.2]
>   over a maximum of 30 hops:
>
>     1   <10 ms   <10 ms   <10 ms  192.168.5.1     <========== local
> WAN router
>     2    50 ms    50 ms    50 ms  203.204.6.72    <========== remote
> WAN router
>     3    50 ms   60 ms    50 ms  server1 [192.168.1.2]
>
>   Trace complete.
>
> This works as expected until the WAN link is down for any amount of
> time. Once the WAN link has been down for a period of more than approx
> 1 hour the workstations lose connectivity with the remote subnet.
> When I run the "route print" command I can still see the persistent
> route listed but on running tracert to a host on the other subnet the
> traffic is routed via the default gateway (internet connection via
> ISP) rather than the internal WAN gateway.
>
> If I re-run the route command above the route is restored and
> connectivity re-instated. It is almost as if there is a timeout where
> after a specified time windows stops attempting to access that subnet
> via the specified static route and defaults to the default gateway.
> This seems to be incorrect, if a route is persistent then windows
> should keep re-trying until the connection is restored or produce an
> error message to inform the user the route is no longer available (on
> screen or event log).
>
> My questions are:
>
> 1.Does anyone know why it is defaulting to the default gateway when
> the persistent route loses connectivity?
>
> 2. Does anyone know how to prevent this default gateway fall back
> (registry or network properties setting)?
>
> 3. Should windows utilise the default gateway when connectivity is
> lost to a host accessible via a previously persistent route?
>
> 4. Why does it still list (ROUTE PRINT) the persistent route even
> though it is no longer using  it due to loss of connectivity?
>
> I have looked on the MS KB and searched on google but it does not seem
> to be mentioned anywhere. Any hints would be appreciated.
>
> Thanks in advance

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: Keep routing table
    ... > the route taken for the return path, you only control the outbound path. ... > one is manually entered in the Routing Table. ... > You can only have *one* Default Gateway. ... > Phillip Windell ...
    (microsoft.public.win2000.networking)
  • Re: VPN and remote gateway
    ... > It seems you use the wrong route add command. ... > when the VPN connection is established. ... > | using the remote network as my gateway. ...
    (microsoft.public.windows.server.sbs)
  • Re: two nics to one lan
    ... > The link may have come back up, but all connectivity was hosed. ... > normal, and the routing table was also normal, which I believe is the ... Whatever happened caused the eth1 route to be non-functional, ... > routing configuration. ...
    (comp.os.linux.networking)