DHCP Fault Tolerance

[genghiz]

Hello friends:

We currently have one DHCP server in windows server 2003 AD environment. I
am planning on splitting the current scopes into two and set up a second
DHCP server for fault-tolerance. My question is how can I get the clients to
request IP address from both the DHCPs.

Thanks.

 

[Meinolf Weber [MVP-DS]]

Hello genghiz,

You can not fix a DHCP server for the clients. If you split the scopes you
will see, that both will be used. First com, first serv is the princip in
DHCP.

We use it also that way and it works fine, both DHCP servers are used.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[Richard G. Harper]

The way DHCP works is that the client sends a broadcast message requesting
an address and the first server to respond gets to issue the address.
There's no way to force a client to use one, or the other, or both DHCP
servers.

 

[genghiz]

Meinolf and richard, muchos gracias.

The way DHCP works is that the client sends a broadcast message requesting
an address and the first server to respond gets to issue the address.
There's no way to force a client to use one, or the other, or both DHCP
servers.

 

[Marcin]

As Meinolf and Richard have stated, DHCP clients will simply use the DHCP
server that responds first to their requests. You can somewhat make this
process more deterministic by placing each DHCP server closer (in terms of
networking distance) to the clients that you intend to target, which
increases probability that its response will get to clients first (but does
not guarantee it). Keep in mind that you need to configure your routers to
allow DHCP communication to get through to other subnets...

hth
Marcin

 

[Vizoere]

Several years back at a different job, I configured DHCP on two clustered
servers. Both servers were configured with the same scopes and such but the
DHCP database was hosted on a shared SAN drive so that if one box failed, the
other box would start the DHCP service and continue right where the other one
left off.

If you're not looking for load balancing, but just failover in case one
server goes down, this solution worked well for me.

:
[snip]

planning on splitting the current scopes into two and set up a second
DHCP server for fault-tolerance.

[snip]

 

[Jorge de Almeida Pinto [MVP - DS]]

also see:
http://blogs.dirteam.com/blogs/jorge/archive/2005/11/24/155.aspx


--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Identity & Access - Directory Services #

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx