>-----Original Message-----
>But you can't authorize NT4 DHCP server, as they have no
knowledge od Active
>Directory. See
>http://www.microsoft.com/windows2000...ver/help/defau
lt.asp?
url=/windows2000/en/server/help/sag_DHCP_imp_AuthorizingSe
rvers.htm
>and the note at the end of the page.
>
>--
>Regards
>
>Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
>(E-Mail Removed)
>http://ladava.com
>
>"Cary Shultz" <(E-Mail Removed)> wrote in message
>news:107d01c386ee$c1753bd0$(E-Mail Removed)...
>>
>> >-----Original Message-----
>> >I am having an issue authorizing NT4 PDC servers in a
>> >newly upgraded AD child domain. Does anyone have any
>> >insight into this?
>> >
>> >We have only 2 AD controllers at one site in the new
>> child
>> >domain. The other NT4 PDC DHCP servers are serving
>> remote
>> >subnets. Attempts to authorize the NT 4 servers using
>> the
>> >AD DHCP snapin on the AD controllers are failing.
>> >
>> >Jim
>> >.
>> Jim,
>>
>> I am sure that this is just a "language" thing, but
there
>> can not be any PDCs in a WIN2000 AD Domain. I think
that
>> you might be confusing this with the FSMO Role of PDC
>> Emulator ( which acts as the WINNT PDC for any WINNT 4
>> BDCs that you might have - naturally if this is a
native
>> Mode AD Domain then there are no WINNT BDCs ).
>>
>> You have to do this when logged in as the Enterprise
>> Administrator ( which, by default, would include
>> the "Administrator" account from the "Root" domain -
aka,
>> the first AD Domain in the Forest ). You can not do
this
>> when logged on as the administrator from the Child
Domain
>> as this account is not part of the Enterprise
>> Administrators group.
>>
>> HTH,
>>
>> Cary
>
>
>.
Thank you, Matjaz!
Clearly you can not do that. His statement
about "authorizing NT4 PDC Servers in a newly upgraded AD
Child Domain" lead me to believe that his terminology was
a bit off. I should have included the part about not
being able to authorize NT4 DHCP Servers in an AD Domain.
Cary
Similar Threads
