From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0221_01C39D5B.4AF4D550
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   You can have multiple IP addresses per-adapter.  One way this is done =
in other applications is to have a non-shared IP for each computer.  =
These could be fixed.  The shared IP used for fail-over is assigned to =
one or the other in addition to its own IP.

Rich

  "Gregg Nemesure"  wrote in message =
news:3f9ed0dd$1{at}w3.nls.net...
  "Jeff Shultz"  wrote in message
  news:3f9ecfae$1{at}w3.nls.net...

  > Meanwhile, it sounds a bit like you've reinvented the wheel - if you
  > want to tie a specific address to a specific machine, you can either
  > give it that address as a static one (which apparently you don't =
want)
  > or configure DHCP to hand out that address only to the MAC address =
of
  > the adapter.
  >

  Not really reinventing the wheel. The two machines are actually single =
board
  computers operating in an environment in which there is no DHCP =
server, and
  the two must be able to decide for themselves, based on mutual =
agreement at
  run-time, which will get the single IP address. This is for a failover
  mechanism.

  Gregg


------=_NextPart_000_0221_01C39D5B.4AF4D550
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   You can
have multiple IP =
addresses=20
per-adapter.  One way this is done in other applications is to have = a=20
non-shared IP for each computer.  These could be fixed. 
The = shared IP=20
used for fail-over is assigned to one or the other in addition to its = own=20
IP.
 
Rich
 

  "Gregg Nemesure" <nemesure{at}mindspring.com>">mailto:nemesure{at}mindspring.com">nemesure{at}mindspring.com>
= wrote in=20
  message news:3f9ed0dd$1{at}w3.nls.net..."Jeff=20
  Shultz" <jeffshultz{at}wvi.com>=20">mailto:jeffshultz{at}wvi.com">jeffshultz{at}wvi.com>=20
  wrote in messagenews:3f9ecfae$1{at}w3.nls.net...=
>=20
  Meanwhile, it sounds a bit like you've reinvented the wheel - if =
you>=20
  want to tie a specific address to a specific machine, you can =
either>=20
  give it that address as a static one (which apparently you don't =
want)>=20
  or configure DHCP to hand out that address only to the MAC address =
of>=20
  the adapter.>Not really reinventing
the wheel. The two =
machines=20
  are actually single boardcomputers operating in an environment in =
which=20
  there is no DHCP server, andthe two must be able to decide for =
themselves,=20
  based on mutual agreement atrun-time, which will get the single IP =

  address. This is for a=20
failovermechanism.Gregg

------=_NextPart_000_0221_01C39D5B.4AF4D550--

--- BBBS/NT v4.01 Flag-5