PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Sat, 12 Jan 2002 02:46:24 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines)
On 12 Jan 2002, at 1:19, Nostradamus Systems wrote:

> I have 8 PC's using Windows ME sharing a leased line for internet
> access.
>
> I have three hubs - which are connected - one with a router for
> the leased line and other kit, and the other two each have 4 PC's
> and an ISDN Router.
>
> Each group of 4 PC's share an ISDN connection if the leased line
> fails.
>
> The PC's  have a static IP address,  and in order to use one of
> the ISDN routers, the DNS Server, Gateway and IP address must be
> changed in the network settings.
>
> Is it possible to automate a process to change these settings,  or
> two "switch" to another configuration?
>
> TIA
>
> Geoff Gant

  There *are* packages which will let you select between several
networking configurations.  Unfortunately, I think most of them let
you make this choice only as part of the boot process, so a change
still means a reboot....

  The more usual "commercial grade" failover solution is for an ISDN
link to parallel the leased line, connecting to a second outside
interface on the same router as the leased line -- running OSPF if it
connects to the same router at the ISP's end as the leased line, and
BGP if it connects to a different router or different ISP.  So the
switchover occurs automatically in a few routing tables, without any
IP address or gateway changes.

1.  You generally shouldn't have to change DNS server addresses.  Is
there some reason you think you need to?

2.  Putting the alternative connections on the other side of a router
from the workstations, with NAT done at the router, should mean you
never have to change a workstation IP address.

3.  In a case where the actual gateway changes, rather than update
the gateway setting on each workstation, I point them all at a router
which may not really be a gateway itself at all, but "knows" -- via
OSPF or some other means -- about what gateways should currently be
used.

  It should be possibke to get the effect you need without making
these changes on every workstation.

David Gillett

               The NOSPIN Group Promotions is now offering
              Mandrake Linux or Red Hat Linux CD sets along
         with our NOSPIN Power Linux CD...  at a great price!!!
             http://freepctech.com/goodies/promotions.shtml

ATOM RSS1 RSS2