Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 355
  • Last Modified:

2 Windows 2003 Domain Controllers, 1 DHCP Scope?

Is it possible to have 2 domain controllers share the same scope?  We would like to implement some sort of fail safe in case one of the domain controllers would die.  
0
AzagThothe
Asked:
AzagThothe
  • 2
  • 2
1 Solution
 
merowingerCommented:
yes u can configure it like this

Server1 has Scope 192.168.1.0
Address Pool from:  192.168.1.1 - 192.168.1.125
Exclusions Range: 192.168.1.126 - 192.168.1.255

Server2 has Scope 192.168.1.0
Address Pool: from192.168.1.126 - 192.168.1.255
Exclusions range: 192.168.1.1 - 192.168.1.125
0
 
ormerodrutterCommented:
But that wasn't sharing a same scope?
DHCP server needs to be authorised before they can server clients. So if you setup DHCP on server2 using the same scope of server1, but leave it UNAUTHORISED - which means server1 will be your only DHCP server. If it dies, just go to server2 and authorise DHCP.
0
 
Mark WaldenInformation Security EngineerCommented:
Are you running DHCP service on your DC's.  I would not recommend this.  Domain controllers are to important to the business.  DHCP does not require much overhead so i would get a midrange server to run this on.  I understand some business want to keep cost down, but the IT department is not the place to do it.  But back to you question, Merowinger is correct.  He is suggesting the 80/20 rule.
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cncb_dhc_ogjw.mspx?mfr=true
 
But i would still put DHCP on another box.
0
 
ormerodrutterCommented:
But don't you think if server1 broke down, server2 will NOT give out the first lots of addresses?
0
 
Mark WaldenInformation Security EngineerCommented:
Well, this is all a mater of opinion as how to set up failover for DHCP.  DHCP is a low power service that is free with the Server OS.  I guess depends on the size of your network.  For a small network I would suggest backing up the database to an external source nightly.  You would only need 1 server to run DHCP.  If the server fails, simply install DHCP on another server through Add/Remove Windows components and apply the database.  For a large net such as the one I work with, I have the DHCP database stored on a SAN with 2 Clustered boxes pointing to the database.  If DHCP1 fails, the cluster will fire up the DHCP service on DHCP2 and uses the same database.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now