"robertj" <(E-Mail Removed)> wrote in message
news:d2b401c439c1$9a688930$(E-Mail Removed)...
> First my question;
> What harm can having 2 DHCP servers on my small network
> do?(28 clients, 3 servers, 2 switches, 1 firewall)
Nothing if done properly
> Can it cause clients to lose connection to thier servers,
Yes
> corrupt data, cause wierd error messages?
Corrupt data, no,....weird errors, maybe yes
> Last night I noticed that we have 2 DHCP servers on our
> network. The vendor who installed our network and
> hardware configured our FIREWALL to act as a DHCP server
> (scope 10.0.0.70 to 10.0.0.139, 60 minute lease) and they
> configured our FILE SERVER (W2K SP4)(scope 10.0.0.100 to
> 10.0.0.200, 1 week lease) to act as a DHCP server.
>
> From the research i've done thus far, it appears that
> only one DHCP server should be live on my network.
> I've stopped the DHCP service on the FILE SERVER and at
> this time only the FIREWALL is serving as DHCP.
As long as they don't each try to give out the same addresses you would be
fine. forexample:
DHCP #1 grants 10.0.200.1 through 10.0.200.254
Exclusions 10.0.200.128 through 10.0.200.254
DHCP #2 grants 10.0.200.1 through 10.0.200.254
Exclusions 10.0.200.1 through 10.0.200.127
Additional Exclusions (identical on both) 10.0.200.1 through 10.0.200.10
Each DHCP Servers gives out half of the possible addresses. Both of them
exclude and don't use the first 10 addresses whic allows these first 10 to
be used for static assignments to other Servers and such.
However I would ditch the DHCP on the Firewall and stay with the Window's
DHCP(especially if running two) since it is more flexable and you have more
control over it.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com