Peculiar DHCP actions

Our corporate network is comprised of two main parts connected by a
wireless link. Each side has a DHCP server handing out address in non-
overlapping pools. One side has 10% of the computers, the other side
(obviously) has the other 90%.

Why does the DHCP server on the side with 10% of the computers wind up
granting about 50% of the addresses? I had always thought that the
first DHCP server answering would grant the IP address. Given the
latency of a 8021.1g link, I would think it would be slow enough to
only grant addresses on it's side of the link.

(Granted I should have some way to stop DHCP requests from traveling
the link, but I don't.)

Any explainations why this is happening?

Dave

You should only have one DHCP server on any given network. If you really want
to know what's happening, fire up WireShark and do some sniffing.

"DaveInPNG" <CTS-(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Our corporate network is comprised of two main parts connected by a
> wireless link. Each side has a DHCP server handing out address in non-
> overlapping pools. One side has 10% of the computers, the other side
> (obviously) has the other 90%.
>
> Why does the DHCP server on the side with 10% of the computers wind up
> granting about 50% of the addresses? I had always thought that the
> first DHCP server answering would grant the IP address. Given the
> latency of a 8021.1g link, I would think it would be slow enough to
> only grant addresses on it's side of the link.
>
> (Granted I should have some way to stop DHCP requests from traveling
> the link, but I don't.)
>
> Any explainations why this is happening?
>
> Dave
>