>
> "SHachborn" <SHachborn[ at ]discussions.microsoft.com> wrote in message
> news:13FBCCD0-1415-483A-908F-B2EEA7EAF6C5[ at ]microsoft.com...
> > Sorry Herb probably did not give you enough info, our ERP system is
> > Oracle
> > and it is printing though Unix and needs the same Ip address all the time,
> > using a reservation on this and our primary DHCP fails it would get the ip
> > from the backup range and this would not match for printing.
>
> No, I basically had all of that. Use Windows Server DHCP; give a
> reservation to each device which assigns the same address; then configure
> the Windows DHCP server to do the registrations in DNS.
>
> This is precisely what I indicated before and what we do.
>
> > For Switches
> > and TS devices we were thinking of setting the reservations on the primary
> > and on the backup DHCP boxes.
>
> Reservations can be set on every DHCP server offering addresses on the
> same scope* -- this way they get the same and correct address no matter
> which DHCP server gives it out.
>
> * Every DHCP server offering on the same subnet should configure
> PRECISELY the same range(s) of addresses (same scope definitions)
> and then exclude those address that this DHCP server must not lease.
>
> This prevents one DHCP server "NAQ"ing the address requests or
> renewals of the other(s).
>
>
> > Thought there might be a Kiss theory that most people are using for all
> > these instances.
> >
>
> Yes. The above works quite simply. (It also allows for SECURE dynamic
> updates even for non-domain machines since the DHCP server is authenticated
> in the domain.)
>
> --
> Herb Martin, MCSE, MVP
>
http://www.LearnQuick.Com> (phone on web site)
>
>
>