PDC Failing and GP not updating

From: "Betzold, Adam" <abetzold@xxxxxxxxx>
Date: Mon, 07 Jul 2008 10:39:17 -0500

I have a somewhat new additional DC in production however the FSMOCheck is failing for it's PDC and I get an error when trying to access the GP. I have included a DCDiag, I can not determine the cause for this. The DCs are connected across a high speed WAN. Any help is much appreciated, thanks in advance.

Domain Controller Diagnosis

Performing initial setup:
* Connecting to directory service on server DRS-689-10.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 3 DC(s). Testing 3 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DRS-343-10A
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DRS-343-10A passed test Connectivity

Testing server: Default-First-Site-Name\DRS-343-10B
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DRS-343-10B passed test Connectivity

Testing server: Default-First-Site-Name\DRS-689-10
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DRS-689-10 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DRS-343-10A
Starting test: Replications
* Replications Check
* Replication Latency Check
The replications latency check is not available on this DC.
* Replication Site Latency Check
......................... DRS-343-10A passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for CN=Schema,CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... DRS-343-10A passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... DRS-343-10A passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=drs343,DC=drs
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=drs343,DC=drs
(Configuration,Version 2)
* Security Permissions Check for
DC=drs343,DC=drs
(Domain,Version 2)
......................... DRS-343-10A passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... DRS-343-10A passed test NetLogons
Starting test: Advertising
The DC DRS-343-10A is advertising itself as a DC and having a DS.
The DC DRS-343-10A is advertising as an LDAP server
The DC DRS-343-10A is advertising as having a writeable directory
The DC DRS-343-10A is advertising as a Key Distribution Center
The DC DRS-343-10A is advertising as a time server
The DS DRS-343-10A is advertising as a GC.
......................... DRS-343-10A passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Domain Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role PDC Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Rid Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Infrastructure Update Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
......................... DRS-343-10A passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 3601 to 1073741823
* drs-343-10a.drs343.drs is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2601 to 3100
* rIDNextRID: 2438
* rIDPreviousAllocationPool is 2101 to 2600
......................... DRS-343-10A passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/drs-343-10a.drs343.drs/drs343.drs
* SPN found :LDAP/drs-343-10a.drs343.drs
* SPN found :LDAP/DRS-343-10A
* SPN found :LDAP/drs-343-10a.drs343.drs/DRS343
* SPN found :LDAP/a37e1493-32f0-407d-b97f-f42c82ec40ee._msdcs.drs343.drs
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a37e1493-32f0-407d-b97f-f42c82ec40ee/drs343.drs
* SPN found :HOST/drs-343-10a.drs343.drs/drs343.drs
* SPN found :HOST/drs-343-10a.drs343.drs
* SPN found :HOST/DRS-343-10A
* SPN found :HOST/drs-343-10a.drs343.drs/DRS343
* SPN found :GC/drs-343-10a.drs343.drs/drs343.drs
......................... DRS-343-10A passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... DRS-343-10A passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
......................... DRS-343-10A passed test OutboundSecureChannels
Starting test: ObjectsReplicated
DRS-343-10A is in domain DC=drs343,DC=drs
Checking for CN=DRS-343-10A,OU=Domain Controllers,DC=drs343,DC=drs in domain DC=drs343,DC=drs on 3 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs in domain CN=Configuration,DC=drs343,DC=drs on 3 servers
Object is up-to-date on all servers.
......................... DRS-343-10A passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... DRS-343-10A passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... DRS-343-10A passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... DRS-343-10A passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... DRS-343-10A passed test systemlog
Starting test: VerifyReplicas
......................... DRS-343-10A passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=DRS-343-10A,OU=Domain Controllers,DC=drs343,DC=drs and backlink on

CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs

are correct.
The system object reference (frsComputerReferenceBL)

CN=DRS-343-10A,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=drs343,DC=drs

and backlink on CN=DRS-343-10A,OU=Domain Controllers,DC=drs343,DC=drs

are correct.
The system object reference (serverReferenceBL)

CN=DRS-343-10A,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=drs343,DC=drs

and backlink on

CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs

are correct.
......................... DRS-343-10A passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
......................... DRS-343-10A passed test VerifyEnterpriseReferences

Testing server: Default-First-Site-Name\DRS-343-10B
Starting test: Replications
* Replications Check
* Replication Latency Check
The replications latency check is not available on this DC.
* Replication Site Latency Check
......................... DRS-343-10B passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for CN=Schema,CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... DRS-343-10B passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... DRS-343-10B passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=drs343,DC=drs
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=drs343,DC=drs
(Configuration,Version 2)
* Security Permissions Check for
DC=drs343,DC=drs
(Domain,Version 2)
......................... DRS-343-10B passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... DRS-343-10B passed test NetLogons
Starting test: Advertising
The DC DRS-343-10B is advertising itself as a DC and having a DS.
The DC DRS-343-10B is advertising as an LDAP server
The DC DRS-343-10B is advertising as having a writeable directory
The DC DRS-343-10B is advertising as a Key Distribution Center
The DC DRS-343-10B is advertising as a time server
The DS DRS-343-10B is advertising as a GC.
......................... DRS-343-10B passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Domain Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role PDC Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Rid Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Infrastructure Update Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
......................... DRS-343-10B passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 3601 to 1073741823
* drs-343-10a.drs343.drs is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1601 to 2100
* rIDNextRID: 1611
* rIDPreviousAllocationPool is 1601 to 2100
......................... DRS-343-10B passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/drs-343-10b.drs343.drs/drs343.drs
* SPN found :LDAP/drs-343-10b.drs343.drs
* SPN found :LDAP/DRS-343-10B
* SPN found :LDAP/drs-343-10b.drs343.drs/DRS343
* SPN found :LDAP/9261c24e-6c89-427d-b152-78381398cde1._msdcs.drs343.drs
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/9261c24e-6c89-427d-b152-78381398cde1/drs343.drs
* SPN found :HOST/drs-343-10b.drs343.drs/drs343.drs
* SPN found :HOST/drs-343-10b.drs343.drs
* SPN found :HOST/DRS-343-10B
* SPN found :HOST/drs-343-10b.drs343.drs/DRS343
* SPN found :GC/drs-343-10b.drs343.drs/drs343.drs
......................... DRS-343-10B passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... DRS-343-10B passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
......................... DRS-343-10B passed test OutboundSecureChannels
Starting test: ObjectsReplicated
DRS-343-10B is in domain DC=drs343,DC=drs
Checking for CN=DRS-343-10B,OU=Domain Controllers,DC=drs343,DC=drs in domain DC=drs343,DC=drs on 3 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=DRS-343-10B,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs in domain CN=Configuration,DC=drs343,DC=drs on 3 servers
Object is up-to-date on all servers.
......................... DRS-343-10B passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... DRS-343-10B passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... DRS-343-10B passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... DRS-343-10B passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... DRS-343-10B passed test systemlog
Starting test: VerifyReplicas
......................... DRS-343-10B passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=DRS-343-10B,OU=Domain Controllers,DC=drs343,DC=drs and backlink on

CN=DRS-343-10B,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs

are correct.
The system object reference (frsComputerReferenceBL)

CN=DRS-343-10B,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=drs343,DC=drs

and backlink on CN=DRS-343-10B,OU=Domain Controllers,DC=drs343,DC=drs

are correct.
The system object reference (serverReferenceBL)

CN=DRS-343-10B,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=drs343,DC=drs

and backlink on

CN=NTDS Settings,CN=DRS-343-10B,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs

are correct.
......................... DRS-343-10B passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
......................... DRS-343-10B passed test VerifyEnterpriseReferences

Testing server: Default-First-Site-Name\DRS-689-10
Starting test: Replications
* Replications Check
* Replication Latency Check
CN=Schema,CN=Configuration,DC=drs343,DC=drs
Latency information for 1 entries in the vector were ignored.
0 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 1 had no latency information (Win2K DC).
CN=Configuration,DC=drs343,DC=drs
Latency information for 1 entries in the vector were ignored.
0 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 1 had no latency information (Win2K DC).
DC=drs343,DC=drs
Latency information for 1 entries in the vector were ignored.
0 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 1 had no latency information (Win2K DC).
* Replication Site Latency Check
......................... DRS-689-10 passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for CN=Schema,CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... DRS-689-10 passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Configuration,DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=drs343,DC=drs.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... DRS-689-10 passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=drs343,DC=drs
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=drs343,DC=drs
(Configuration,Version 2)
* Security Permissions Check for
DC=drs343,DC=drs
(Domain,Version 2)
......................... DRS-689-10 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... DRS-689-10 passed test NetLogons
Starting test: Advertising
The DC DRS-689-10 is advertising itself as a DC and having a DS.
The DC DRS-689-10 is advertising as an LDAP server
The DC DRS-689-10 is advertising as having a writeable directory
The DC DRS-689-10 is advertising as a Key Distribution Center
The DC DRS-689-10 is advertising as a time server
The DS DRS-689-10 is advertising as a GC.
......................... DRS-689-10 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Domain Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role PDC Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Rid Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs
Role Infrastructure Update Owner = CN=NTDS Settings,CN=DRS-343-10A,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs

......................... DRS-689-10 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 3601 to 1073741823
* drs-343-10a.drs343.drs is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 3101 to 3600
* rIDPreviousAllocationPool is 3101 to 3600
* rIDNextRID: 3107
......................... DRS-689-10 passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/drs-689-10.drs343.drs/drs343.drs
* SPN found :LDAP/drs-689-10.drs343.drs
* SPN found :LDAP/DRS-689-10
* SPN found :LDAP/drs-689-10.drs343.drs/DRS343
* SPN found :LDAP/af71a11f-b6e5-4096-839f-d94bd27c1402._msdcs.drs343.drs
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/af71a11f-b6e5-4096-839f-d94bd27c1402/drs343.drs
* SPN found :HOST/drs-689-10.drs343.drs/drs343.drs
* SPN found :HOST/drs-689-10.drs343.drs
* SPN found :HOST/DRS-689-10
* SPN found :HOST/drs-689-10.drs343.drs/DRS343
* SPN found :GC/drs-689-10.drs343.drs/drs343.drs
......................... DRS-689-10 passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... DRS-689-10 passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
......................... DRS-689-10 passed test OutboundSecureChannels
Starting test: ObjectsReplicated
DRS-689-10 is in domain DC=drs343,DC=drs
Checking for CN=DRS-689-10,OU=Domain Controllers,DC=drs343,DC=drs in domain DC=drs343,DC=drs on 3 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=DRS-689-10,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs in domain CN=Configuration,DC=drs343,DC=drs on 3 servers
Object is up-to-date on all servers.
......................... DRS-689-10 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... DRS-689-10 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... DRS-689-10 passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... DRS-689-10 passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... DRS-689-10 passed test systemlog
Starting test: VerifyReplicas
......................... DRS-689-10 passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=DRS-689-10,OU=Domain Controllers,DC=drs343,DC=drs and backlink on

CN=DRS-689-10,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs

are correct.
The system object reference (frsComputerReferenceBL)

CN=DRS-689-10,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=drs343,DC=drs

and backlink on CN=DRS-689-10,OU=Domain Controllers,DC=drs343,DC=drs

are correct.
The system object reference (serverReferenceBL)

CN=DRS-689-10,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=drs343,DC=drs

and backlink on

CN=NTDS Settings,CN=DRS-689-10,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=drs343,DC=drs

are correct.
......................... DRS-689-10 passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
......................... DRS-689-10 passed test VerifyEnterpriseReferences

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : drs343
Starting test: CrossRefValidation
......................... drs343 passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... drs343 passed test CheckSDRefDom

Running enterprise tests on : drs343.drs
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope

provided by the command line arguments provided.
......................... drs343.drs passed test Intersite
Starting test: FsmoCheck
GC Name: \\drs-689-10.drs343.drs
Locator Flags: 0xe00003fc
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Time Server Name: \\drs-689-10.drs343.drs
Locator Flags: 0xe00003fc
Preferred Time Server Name: \\drs-689-10.drs343.drs
Locator Flags: 0xe00003fc
KDC Name: \\drs-689-10.drs343.drs
Locator Flags: 0xe00003fc
......................... drs343.drs failed test FsmoCheck
.

Follow-Ups:
- Re: PDC Failing and GP not updating
  - From: Meinolf Weber

Prev by Date: Re: Server 2003 sp3 error - Domain controller cannot be found ?
Next by Date: Re: Domain can not be found
Previous by thread: Domain can not be found
Next by thread: Re: PDC Failing and GP not updating
Index(es):
- Date
- Thread

Relevant Pages

Re: PDC Failing and GP not updating
... Replication Latency Check ... Analyzing the connection topology for ... Performing upstream analysis. ... Performing downstream (of target) analysis. ...
(microsoft.public.windows.server.active_directory)
Re: PDC Failing and GP not updating
... Replication Latency Check ... Configuration Topology Integrity Check ... Performing upstream analysis. ... Performing downstream (of target) analysis. ...
(microsoft.public.windows.server.active_directory)
Re: Cached Credentials causing problems with shares?
... Replication Latency Check ... Performing upstream analysis. ... Performing downstream (of target) analysis. ...
(microsoft.public.windows.server.active_directory)
Re: AD Replication fails with RPC error
... Verifying that the local machine tahoe, ... Replication Site Latency Check ... Performing upstream analysis. ... Performing downstream (of target) analysis. ...
(microsoft.public.windows.server.active_directory)
Re: AD Replication fails with RPC error
... Connecting to directory service on server tahoe. ... Replication Site Latency Check ... Performing upstream analysis. ... Performing downstream (of target) analysis. ...
(microsoft.public.windows.server.active_directory)