The role owner attribute could not be read when promoting server

[Al Jackson]

"The role owner attribute could not be read." when
promoting server to DC for new child domain. This happens
when attempting to join any server as a DC in any new
child domain, so I'm guessing the problem is something to
do with the DC in the parent domain.

I have gone so far as to put the existing DC and the new
server on their own switch and isolate them from the rest
of the network, (in order to rule out routers or firewalls
blocking traffic) but the same results occur everytime.
I've re-applied service packs, verified roles, review DNS,
everything seems o.k.....

I have searched EVERYWHERE and I can't find squat, anyone
else run into this problem before?

 

[Matjaz Ladava [MVP]]

This is probably a DNS issue, or Domain naming master FSMO role can not be
conntacted in your forest. Use netdom query fsmo, to locate your FSMO
holders and then verify, that the computer you are trying to promote can
conntact this fsmo role owner. Use nslookup to verify connectivity.

--

Regards

Matjaz Ladava, MCSA, MCSE, MCT, MVP
Microsoft MVP Windows Server - Active Directory
(e-mail address removed), (e-mail address removed)