Alvaro Zuniga <[EMAIL PROTECTED]> writes: > I do not know to much about this but if your are using different address > pools > like you have stated this is how is see it: > > In order to have a conflict the DHCP discovery algorithm would have to find a > second instance of the DHCP server after finding the first one :-) Sounds > like a Microsoftian Alnorythm. >
It's not as uncommon as you might think. I set up failover DHCP servers when I was employed at Charter using Cisco's CNR. It's also possible to do this with ISC dhcpd. You can also have two machines handing out different pools. The main thing is each machine needs to be aware of the other's pools and leases. As long as the dhcp client gets a valid lease, it doesn't know or care about the multiple DHCP servers on the subnet. Regarding the original poster's issues, I would turn off one of the DHCP servers in his subnet. There's really no reason to have two running in a small office environment and it will make problem resolution really hard for him to diagnose. -- Scott Harney<[EMAIL PROTECTED]> "...and one script to rule them all."
