Hi Syedali,
This behavior can be caused by inconsistency in the domain naming master
role owner as seen by different domain controllers in the forest because of
replication latency or problems. Use the following troubleshooting steps to
determine if a problem exists:
Confirm that the domain naming master is replicating Active Directory. Type
repadmin /showreps at a command prompt.
Domain controllers in the forest are consistent about the computer name
that is designated as the current domain naming master.
Confirm that the domain naming master is a global catalog server. Type
nltest /dsgetdc:domainname /server:servername to see if the server is
advertising the "GC" flag. New global catalog servers also register event
1119 ("This Windows domain controller is a now a global catalog server").
MORE INFORMATION
===================
The domain naming master FSMO role holder is the only computer that can add
or remove a domain in a Windows 2000 Active Directory forest, and is the
only FSMO role owner contacted by the Active Directory Installation Wizard
(Dcpromo.exe). No FSMO role access is required to promote or demote replica
domain controllers in an existing domain.
Investigate Domain Name System (DNS) name resolution, network connectivity,
and consistency in Active Directory for the current domain naming master
FSMO role holder when "naming master" or "FSMO" error messages occur during
Dcpromo operations.
Syedali, also for more information look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;254933&Product=win20
00
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
