Whilst you can just define the ranges, I would prefer to specify a proper subnet/netmask definition, and add the appropriate exclusions. It's easier to automate using netsh.exe as well (if you are going to be typing things in at a command line)
Cheers Ken From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, 15 September 2008 10:29 PM To: NT System Admin Issues Subject: RE: DHCP fail-over Oh I'm aware we could expand the range, part of which will be done with the 2nd DHCP, but where possible we try to put in as much redundancy as we can, and DHCP a good target for that now. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: 15 September 2008 13:17 To: NT System Admin Issues Subject: RE: DHCP fail-over So? Expand the range. As for your original question, your conclusion is correct. They don't actually need to be excluded. Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael Link with me at: http://www.linkedin.com/in/theessentialexchange From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2008 7:53 AM To: NT System Admin Issues Subject: RE: DHCP fail-over We have a large number of freelancers and transient workers. With long lease times we sometimes hit the limit of the lease range on the server. Keeping it short means that the IPs are available again for us more quickly. From: Steve Moffat [mailto:[EMAIL PROTECTED] On Behalf Of NTSysAdmin Sent: 15 September 2008 12:31 To: NT System Admin Issues Subject: RE: DHCP fail-over Why are your leases so short?? S From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2008 6:50 AM To: NT System Admin Issues Subject: DHCP fail-over Hi chaps, I'm looking at setting up DHCP failover on our two servers here so that if one goes down (as it did this morning) the DHCP leases wont expire and chop off the workstations at the legs. On the web it seems fairly easy in 2003 so thats a good thing. However can someone confirm something for me? It seems to be that I need to add both machines to the DNSUpdateProxy group and that each machine needs to be (can be) setup using the same scope details. However, each machine needs to have excluded the other machines part of the IP range ? That is, if serverA does .1-.50 then ServerB needs 1-50 in the exclusion and if ServerB does 51-100 then ServerA needs 51-100 in it's exclusion. Is that right? My question is really whether it has to be an exclusion or whether I can simply set the range up each box so that A has a range of 1-50 and B has a range of 51-100. Any ideas ? Olly ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
