We had this same issue recently. We had a Windows 2003 server acting as a
DHCP server that was a member of our corporate domain and it was disconnected
due to an extended WAN outage and it stopped dispensing IP addresses. It
stopped about 48 hours after the outage occured. About 30 minutes after the
WAN connection was restored, the DHCP server again started to function.
Other than this dialogue, I've not been able to find any other documentation
or instances of this type of activity occuring.
Microsoft has documentation that you can use DHCP outside of a domian. But
my guess is that if the windows DHCP server is a member of a domain it cannot
be disconnected from that domain for an extended period of time without the
DHCP server ceasing to function.
"James Yeomans BSc, MCSE" wrote:
> does the dhcp server actually become unauthorized or just stop, i.e. do you
> have to reauthorize it? If it just stops it sounds like it is detecting
> another dhcp server on the network. If it just randomly becomes unauthorized
> then i can't say why that would be.
> James
> --
> James Yeomans, BSc, MCSE
> Ask me directly at: http://www.justaskjames.co.uk
>
>
> "CK" wrote:
>
> > It should be pointing to Corp for primary and secondary DNS and the other DC
> > for a teriary. I was told there is no other dhcp server on the network. What
> > exactly does it detect that could be killing dhcp because nothing else on the
> > network is handing out IP addresses. Is it possible that it is detecting a
> > non configured but active dhcp server on the fw/switch?