LocatorCheck Test Failed -- PDC_REQUIRED


just demoted old pdc , added , promoted new pdc.  dcdiag passed tests before promoting.  have not raised functional level 2008 yet.

i believe scrubbed old pdc dns though have seen show in queries (can't remember which).

dcdiag on pdc still has no errors.

other dcs have error:

warning: dcgetdcname(pdc_required) call failed, error 1355
primary domain controller not located.
server holding pdc role down.

on dcs netdom query fsmo list pdc roles.

on dcs nltest /dclist:domain.com lists correct dc pdc.

the pdc seems authoritative time server.

in dfs management, when try list namespaces receive following error:

\\domain.com\namespace:  namespace cannot queried. specified domain either not exist or not contacted.

replication groups populate.

i need troubleshooting.  thanks


i think forgot delete entry of old dc dns following locations.

manual steps

dnsmgmt.msc [dns management]
 a.expand forward lookup zones\_msdcs folder
 i. make sure actual domain controllers listed, delete wrong alias recordsremove wrong name server records
 ii. select container [forward lookup zones\_msdcs.domain.com\dc\_sites_\sitename\_tcp] > delete incorrect _ldap , _kerberos records listed.
 iii. select container [forward lookup zones\_msdcs.domain.com\dc\_tcp] , delete incorrect _ldap , _kerberos records
 iv. expand [forward lookup zones\_msdcs.domain.com\domains\guid\_tcp] , delete incorrect _ldap entries
 v. select [forward lookup zones\_msdcs.domain.com\gc] – delete incorrect hosta records
 vi. expand [forward lookup zones\_msdcs.domain.com\gc\_sites\sitename\_tcp] – delete incorrect _ldap entries
 vii.select [forward lookup zones\_msdcs.domain.com\gc\_tcp] – delete incorrect _ldap entries
 viii. select [forward lookup zones\_msdcs.domain.com\pdc\_tcp] – delete incorrect _ldap entries
 
 b.expand forward lookup zones\domain.com folder
 i.delete host(a) records of dc’s non-existant.
 ii.correct nameserver (ns) records
 iii. follow steps similar ’ ii ‘ >> ‘ viii’
 
· dssite.msc [sites , services]
 a.expand [sites\sitename\servers] – delete incorrect server’s
 b.delete incorrect subnet configurations [sites\subnets]
 c.delete incorrect site links [sites\ip]
 
 · make sure domain controllers pointing correct dns servers in tcp\ip settings.
 · force replication – ‘repadmin /syncall’



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607