How to correctly split DHCP on flat nework
We have two buildings connected with a fiber cable. These building work on one flat network, unfortunately. The Windows Server 2008 DHCP server is in the first building. We are trying to provide DHCP to the second building if the first building goes off-line.
I have implemented another Windows Server 2008 DHCP server in the second building and it is working ok. At this point users get IPs at random from either server.
Is there a better way to do this on a flat network?
I have implemented another Windows Server 2008 DHCP server in the second building and it is working ok. At this point users get IPs at random from either server.
Is there a better way to do this on a flat network?
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
@xBouchardx
if the connection drops, how do you propose turning on the DHCP server ?
why would you suggest not having both DHCP servers running with suitable exclusions ?
if the connection drops, how do you propose turning on the DHCP server ?
why would you suggest not having both DHCP servers running with suitable exclusions ?
Also, as long as your second building's DHCP server is functioning correctly and you do lose connection to your first building, the clients with leases from the first building's DHCP server will be just fine (as long as you have the same scope options set on both servers, i.e. DNS servers, gateway, WINs, etc.) and when their leases are coming up to expire they will broadcast that they need a new lease at which time the second building's DHCP server will hand out leases. This is also assuming you're going to be down long enough for that to happen.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I tend to not use conflict detection, but instead to just use exclusions....
I would agree with forgetting about 80/20, use 50/50 :-)
I would agree with forgetting about 80/20, use 50/50 :-)
Windows Server 2008
Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.
86K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
1) Create two DHCP servers, which you've already done
2) Create/configure the scopes and options you want for them both on each server, which you've already done
3) Simply turn the DHCP service for the 2nd/backup DHCP server off until a network outtage or other event warrants turning it on. If the first building drops connection to the second or if the first DHCP server fails, turn the DHCP service on the 2nd server on and release/renew client IPs.