A few question.... completely firing in different directions but may lead to a cause :-
 
1) I take it your routers are relaying DHCP, not agents?
2) Is there a local DC in the same subnet as the DHCP server?
3) What are the routers? I've seen different routers play games with DHCP relays.
4) What was the maintenance?
5) Are all your DCs running clean on DCDIAGS ( I know I always ask that question, but 
identifies obvious config issues at times)
 
Rob

________________________________

From: [EMAIL PROTECTED] on behalf of Charlie Kaiser
Sent: Mon 01/11/2004 21:23
To: [EMAIL PROTECTED]
Subject: [ActiveDir] DHCP authorization problem



I had an odd one over the weekend. We did some network maintenance that
included a core switch bounce. Down for about 5 minutes. We found out
this morning that DHCP wasn't working on any subnets except for the one
that the DHCP server was on. We had made switch and router code and
config changes, so we looked to that as a solution, but with no success.
I remembered something from a while back where I had a similar problem
and restarted the DHCP service. This corrected the issue. Apparently,
the DHCP server had lost authorization from AD when the core switch went
down. Event ID 1059; "The DHCP service failed to see a directory server
for authorization." I would have expected it to reauthorize once
connectivity was restored, however. But it didn't. I had to restart the
service manually.
Is this normal? I would expect that DHCP authorization would be able to
recover from a short loss of connectivity.
Any pointers to a way to prevent this from happening again?
Thanks!

**********************
Charlie Kaiser
MCSE, CCNA
Systems Engineer
Essex Credit / Brickwalk
510 595 5083
**********************
List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

=======================================================================
              Scanned for virus infection by Messagelabs
=======================================================================


<<winmail.dat>>

Reply via email to