Hi,
Resource wise a single DHCP server would have no problem is dealing with
the number of addresses in your network, however as you are probably already
thinking this does introduce a single point of failure which should always be
avoided if possible. So using an additional DHCP server would remove this and
provide fault tolerance. The links below should give you all the info you
need:
http://www.windowsdevcenter.com/pub/...CP_Server.html
http://www.microsoft.com/technet/pro...18486db3e.mspx
Cheers
iwsec
http://www.vulnerability-scans.co.uk
http://www.iwsec.co.uk/oscommerce.htm
"
razor" wrote:
> Yes, thank you. We are setting up a secondary DC as the 2nd one pooped out
> and we are decomissioning it. Considering that, what are your thoughts on a
> secondary DHCP server?
>
> Stephen
>
> "Bill Grant" wrote:
>
> > I would rate a second DC as a higher priority than a second DHCP server.
> > Losing a DHCP server is an inconvenience. Losing your only DC is a disaster.
> >
> > razor wrote:
> > > Hello--
> > >
> > > We have about 50 users and about 11 servers. One domain, one Exchange
> > > server, one domain controller and have never had a secondary DHCP
> > > server.
> > >
> > > We have a new IT Manager who wants a secondary DHCP server. I checked
> > > MS TN and couldn't find anything. Does anyone know:
> > >
> > > 1. Does a network of our size need a secondary DHCP server?
> > > 2. If yes, where is an article on how to set that up?
> > >
> > > Many Thanks,
> > >
> > > Stephen
> >
> >
> >