Re: DHCP Authorization
- From: "Dmitry Korolyov [MVP]" <d__k@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 23 Sep 2005 00:06:19 +0400
Try waiting for some time (for this information to replicate to all DCs, or
replicate it manually), then closing and opening mmc console again, and
restarting the DHCP server.
If it shows up as authorized, its ok - just let few minutes pass.
--
Dmitry Korolyov [d__k@xxxxxxxxxxxxxxxxxxxxxx]
MVP: Windows Server - Directory Services
"Regan" <Regan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5792D6FA-E8C1-4D21-A53A-126618AC0E9A@xxxxxxxxxxxxxxxx
> Hello Folks,
>
> I have a domain environment (lab) where DHCP servers, located within
> their
> own child domains, are attempting to authorize. After following the
> correct
> process in authorizing the DHCP server, within a separate child domain,
> the
> "RED" arrow remains; however, the two places indicate that the server have
> been authorized.
>
> First, on the server attempting to authorize, under the DHCP context menu,
> within the dhcpmngmt menu, after select the "ADD Server" menu item, the
> server is listed in the "This Authorized Serer" server list
>
> Second, running "Netsh dhcp show server" command at the command prompt on
> a
> DC in the root domain also indicates that the server is authorized: Or at
> least it is present in the list.
>
> So the problem remains, the supposedly authorized server is still
> indincated as unauthorized. In Addition, it is obviously NOT distributing
> IP
> Addresses
>
> NOTES:
> We are using an enterprise admin for the Authorization process
> All connectivity issues have been eliminated
> DNS entries are up to par
> Root DCs and GCs are ok
>
> Regan
.
- Prev by Date: Re: Questions about FSMO and additional domain controllers
- Next by Date: Re: ADPREP version?
- Previous by thread: Users can't login to domain unless they have admin rights
- Next by thread: Re: AD site replication problems
- Index(es):
Relevant Pages
|
