My work setup had only one Windows 2003 DHCP Server which resides on DC01. I wanted to improve the redundancy for DHCP so I installed DHCP services on another server (DC02) which is also a DC and DNS Server.
Both DHCP servers use the same scope: xxx.xxx.172.20 to xxx.xxx.172.240. Previously DC01 administered leases for the entire scope, however we decided to implement opposite exclusions for the scope.
- DC01 has exclusions xxx.xxx.172.111 to xxx.xxx.172.199
- DC02 has exclusions xxx.xxx.172.21 to xxx.xxx.172.110
With the exclusions activated, no one DHCP server can supply enough leases for all our clients (approximately 140).
The first DHCP server (DC01) continues to provide DHCP leases, but the new DHCP server (DC02) doesn't give out leases even though it is authorised and active.
For testing, I took my PC off the network. We checked DC01 and its leases were at 100%. I did an ipconfig /release and ipconfig /renew however we couldn't get an IP. We only managed to get an internal 169.x.x.x IP.
This xxx.xxx.172 is a vlan, and we have setup iphelpers on the dist switch.
Are we missing anything?
Best Answer
We got this fixed this morning after speaking with our network guy. The iphelpers were confirmed as ok.
furhter investigation on the switch interfaces that the DHCP servers were plugged into showed they didn't have IP DHCP snooping trusetd. the following ** commands were added to the switch interfaces that the DHCP servers were plugged into.
Thanks for the replies.