One NIC, one default GW, incoming connections
- From: "Mika Takala" <mika.takala@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 May 2008 15:46:37 +0300
Hello
I have a LAN where an ADSL router is serving as the
default gateway, and that is the primary, preferred Internet
access for the LAN.
There is also another gateway on the network, and
Internet access is also possible via it.
Both routers are on the same LAN and IP-addresses
are from the 192.168.1.x net. Both routers are setup for NAT.
The computer
(running Windows 2000 Pro SP4)
has a single NIC.
I would like to have some kind of redundancy in accessing the computer on
this network from WAN side. I use approriate port forwarding on the adsl
router and also on the other router, but when the default gateway on the
computer is the adsl router, incoming connections via the other router to
this computer are not possible, as the packets going back get routed
to the default router, not the one the incoming connection is being
routed through.
I could set the other router as another default gateway with higher metric
value. Then the incoming connections from that router will work. The
undesired effect in this option is that when the adsl connection goes down
or the adsl router dies, Windows 2000 automatically selects the other
default gateway. That is not good, as I would only like to use that router
for remote/WAN access. And the ISP in which that router is connected to,
has strict traffic amount restrictions, so p2p etc. connections routed via
it
are very much undesired.
Is there something I could do to disable dead router detection or to maybe
configure my network differently? I've already tried setting
EnableDeadGWDetect=0 for the interface
and
EnableDeadGWDetectDefault=0
in the registry, and making the necessary reboots.
Windows will still, after a short while, switch
to the undesired gateway when the adsl connection dies.
Thanks for any answers,
--
Mika Takala
.
- Follow-Ups:
- Re: One NIC, one default GW, incoming connections
- From: Phillip Windell
- Re: One NIC, one default GW, incoming connections
- Prev by Date: Re: Mass change passwords on service and scheduled tasks
- Next by Date: Win2K can't get out to Internet ... sort of
- Previous by thread: Design of a computer network solution for a given scenario
- Next by thread: Re: One NIC, one default GW, incoming connections
- Index(es):
Relevant Pages
|
