Active Directory Replication Error
Hi Any one can advice me . We have the replication error in our server event viewer( we have two domain controller DC1 and DC2) Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1308 Date: 2/20/2010 Time: 12:33:37 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: CHD1DOMINO1 Description: The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed. Attempts: 13 Domain controller: CN=NTDS Settings,CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Period of time (minutes): 214 The Connection object for this domain controller will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this domain controller resumes, the temporary connection will be removed. Additional Data Error value: 8456 The source server is currently rejecting replication requests. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ############################################################################################ If we try to do a manual replication from the site and services tab. It throw the error message. Below is the error message for your reference. The following error occured during the attempt to synchronize naming context vernalis.com from fomain controller CHD1DOMINO2 domain controller CHD1DOMINO1 The resource server is currently rejecting replication requests. Thanks Alagar.
February 20th, 2010 12:57pm

Hi, Unfortunately we have shutdown DC1(Primary) but DC2(additional is uponly) but we are not able to login from client machines
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2010 1:42pm

on DC2, run net share at a command prompt and post the output please.http://cbfive.com/blog
February 20th, 2010 9:38pm

Hello Alagar Swamy,please post an unedited dcdiag /v from both DCs and also ipconfig /all from both. Are both DCs also DNS and Global catalog server? If not the clients cannot logon as the DNS server isn't available.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
February 21st, 2010 11:16pm

Hi Meinolf Weber, I have posted DC1 and DC2 dcdiag /v Domain Controller Diagnosis Performing initial setup: * Verifying that the local machine chd1domino1, is a DC. * Connecting to directory service on server chd1domino1. * Collecting site info. * Identifying all servers. * Identifying all NC cross-refs. * Found 2 DC(s). Testing 1 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\CHD1DOMINO1 Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check ......................... CHD1DOMINO1 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\CHD1DOMINO1 Starting test: Replications * Replications Check Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled * Replication Latency Check DC=ForestDnsZones,DC=vernalis,DC=com Latency information for 3 entries in the vector were ignored. 3 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=DomainDnsZones,DC=vernalis,DC=com Latency information for 3 entries in the vector were ignored. 3 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). CN=Schema,CN=Configuration,DC=vernalis,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). CN=Configuration,DC=vernalis,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=vernalis,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). * Replication Site Latency Check ......................... CHD1DOMINO1 passed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions check for all NC's on DC CHD1DOMINO1. * Security Permissions Check for DC=ForestDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for DC=DomainDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for CN=Schema,CN=Configuration,DC=vernalis,DC=com (Schema,Version 2) * Security Permissions Check for CN=Configuration,DC=vernalis,DC=com (Configuration,Version 2) * Security Permissions Check for DC=vernalis,DC=com (Domain,Version 2) ......................... CHD1DOMINO1 passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\CHD1DOMINO1\netlogon Verified share \\CHD1DOMINO1\sysvol ......................... CHD1DOMINO1 passed test NetLogons Starting test: Advertising The DC CHD1DOMINO1 is advertising itself as a DC and having a DS. The DC CHD1DOMINO1 is advertising as an LDAP server The DC CHD1DOMINO1 is advertising as having a writeable directory The DC CHD1DOMINO1 is advertising as a Key Distribution Center The DC CHD1DOMINO1 is advertising as a time server The DS CHD1DOMINO1 is advertising as a GC. ......................... CHD1DOMINO1 passed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Domain Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role PDC Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Rid Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com ......................... CHD1DOMINO1 passed test KnowsOfRoleHolders Starting test: RidManager * Available RID Pool for the Domain is 5106 to 1073741823 * chd1domino1.vernalis.com is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 3606 to 4105 * rIDPreviousAllocationPool is 3606 to 4105 * rIDNextRID: 3834 ......................... CHD1DOMINO1 passed test RidManager Starting test: MachineAccount Checking machine account for DC CHD1DOMINO1 on DC CHD1DOMINO1. * SPN found :LDAP/chd1domino1.vernalis.com/vernalis.com * SPN found :LDAP/chd1domino1.vernalis.com * SPN found :LDAP/CHD1DOMINO1 * SPN found :LDAP/chd1domino1.vernalis.com/VERNALIS * SPN found :LDAP/32202f44-cd9b-4322-94b1-2d8486921250._msdcs.vernalis.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/32202f44-cd9b-4322-94b1-2d8486921250/vernalis.com * SPN found :HOST/chd1domino1.vernalis.com/vernalis.com * SPN found :HOST/chd1domino1.vernalis.com * SPN found :HOST/CHD1DOMINO1 * SPN found :HOST/chd1domino1.vernalis.com/VERNALIS * SPN found :GC/chd1domino1.vernalis.com/vernalis.com ......................... CHD1DOMINO1 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 ......................... CHD1DOMINO1 passed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated CHD1DOMINO1 is in domain DC=vernalis,DC=com Checking for CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com in domain DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com in domain CN=Configuration,DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. ......................... CHD1DOMINO1 passed test ObjectsReplicated Starting test: frssysvol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... CHD1DOMINO1 passed test frssysvol Starting test: frsevent * The File Replication Service Event log test ......................... CHD1DOMINO1 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. ......................... CHD1DOMINO1 passed test kccevent Starting test: systemlog * The System Event log test Found no errors in System Event log in the last 60 minutes. ......................... CHD1DOMINO1 passed test systemlog Test omitted by user request: VerifyReplicas Starting test: VerifyReferences The system object reference (serverReference) CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. The system object reference (frsComputerReferenceBL) CN=CHD1DATASERVER1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com are correct. The system object reference (serverReferenceBL) CN=CHD1DATASERVER1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. ......................... CHD1DOMINO1 passed test VerifyReferences Test omitted by user request: VerifyEnterpriseReferences Test omitted by user request: CheckSecurityError Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom 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 : vernalis Starting test: CrossRefValidation ......................... vernalis passed test CrossRefValidation Starting test: CheckSDRefDom ......................... vernalis passed test CheckSDRefDom Running enterprise tests on : vernalis.com Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. ......................... vernalis.com passed test Intersite Starting test: FsmoCheck GC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd PDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Preferred Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd KDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd ......................... vernalis.com passed test FsmoCheck Test omitted by user request: DNS Test omitted by user request: DNS ########################################################################################### Domain Controller Diagnosis Performing initial setup: * Verifying that the local machine chd1domino2, is a DC. * Connecting to directory service on server chd1domino2. * Collecting site info. * Identifying all servers. * Identifying all NC cross-refs. * Found 2 DC(s). Testing 1 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\CHD1DOMINO2 Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check ......................... CHD1DOMINO2 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\CHD1DOMINO2 Starting test: Replications * Replications Check [Replications Check,CHD1DOMINO2] Inbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_INBOUND_REPL" [Replications Check,CHD1DOMINO2] Outbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_OUTBOUND_REPL" ......................... CHD1DOMINO2 failed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions check for all NC's on DC CHD1DOMINO2. * Security Permissions Check for DC=ForestDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for DC=DomainDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for CN=Schema,CN=Configuration,DC=vernalis,DC=com (Schema,Version 2) * Security Permissions Check for CN=Configuration,DC=vernalis,DC=com (Configuration,Version 2) * Security Permissions Check for DC=vernalis,DC=com (Domain,Version 2) ......................... CHD1DOMINO2 passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\CHD1DOMINO2\netlogon Verified share \\CHD1DOMINO2\sysvol ......................... CHD1DOMINO2 passed test NetLogons Starting test: Advertising Warning: DsGetDcName returned information for \\chd1domino1.vernalis.com, when we were trying to reach CHD1DOMINO2. Server is not responding or is not considered suitable. The DC CHD1DOMINO2 is advertising itself as a DC and having a DS. The DC CHD1DOMINO2 is advertising as an LDAP server The DC CHD1DOMINO2 is advertising as having a writeable directory The DC CHD1DOMINO2 is advertising as a Key Distribution Center The DC CHD1DOMINO2 is advertising as a time server ......................... CHD1DOMINO2 failed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Domain Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role PDC Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Rid Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com ......................... CHD1DOMINO2 passed test KnowsOfRoleHolders Starting test: RidManager * Available RID Pool for the Domain is 5106 to 1073741823 * chd1domino1.vernalis.com is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 4606 to 5105 * rIDPreviousAllocationPool is 4106 to 4605 * rIDNextRID: 4401 ......................... CHD1DOMINO2 passed test RidManager Starting test: MachineAccount Checking machine account for DC CHD1DOMINO2 on DC CHD1DOMINO2. * SPN found :LDAP/chd1domino2.vernalis.com/vernalis.com * SPN found :LDAP/chd1domino2.vernalis.com * SPN found :LDAP/CHD1DOMINO2 * SPN found :LDAP/chd1domino2.vernalis.com/VERNALIS * SPN found :LDAP/c965921e-927d-4e64-b32c-b677fdf81c96._msdcs.vernalis.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/c965921e-927d-4e64-b32c-b677fdf81c96/vernalis.com * SPN found :HOST/chd1domino2.vernalis.com/vernalis.com * SPN found :HOST/chd1domino2.vernalis.com * SPN found :HOST/CHD1DOMINO2 * SPN found :HOST/chd1domino2.vernalis.com/VERNALIS * SPN found :GC/chd1domino2.vernalis.com/vernalis.com ......................... CHD1DOMINO2 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 w32time Service is stopped on [CHD1DOMINO2] * Checking Service: NETLOGON NETLOGON Service is paused on [CHD1DOMINO2] ......................... CHD1DOMINO2 failed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated CHD1DOMINO2 is in domain DC=vernalis,DC=com Checking for CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com in domain DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com in domain CN=Configuration,DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. ......................... CHD1DOMINO2 passed test ObjectsReplicated Starting test: frssysvol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... CHD1DOMINO2 passed test frssysvol Starting test: frsevent * The File Replication Service Event log test ......................... CHD1DOMINO2 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. ......................... CHD1DOMINO2 passed test kccevent Starting test: systemlog * The System Event log test An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:26 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:14 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:15 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:16 (Event String could not be retrieved) ......................... CHD1DOMINO2 failed test systemlog Test omitted by user request: VerifyReplicas Starting test: VerifyReferences The system object reference (serverReference) CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. The system object reference (frsComputerReferenceBL) CN=CHD1DOMINO2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com are correct. The system object reference (serverReferenceBL) CN=CHD1DOMINO2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=NTDS Settings,CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. ......................... CHD1DOMINO2 passed test VerifyReferences Test omitted by user request: VerifyEnterpriseReferences Test omitted by user request: CheckSecurityError Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom 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 : vernalis Starting test: CrossRefValidation ......................... vernalis passed test CrossRefValidation Starting test: CheckSDRefDom ......................... vernalis passed test CheckSDRefDom Running enterprise tests on : vernalis.com Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. ......................... vernalis.com passed test Intersite Starting test: FsmoCheck GC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd PDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Preferred Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd KDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd ......................... vernalis.com passed test FsmoCheck Test omitted by user request: DNS Test omitted by user request: DNS
February 22nd, 2010 9:15pm

Hi Meinolf Weber, I have posted DC1 and DC2 dcdiag /c Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\CHD1DOMINO1 Starting test: Connectivity ......................... CHD1DOMINO1 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\CHD1DOMINO1 Starting test: Replications Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled Skipping server CHD1DOMINO2, because it has outbound replication disabled ......................... CHD1DOMINO1 passed test Replications Starting test: Topology ......................... CHD1DOMINO1 passed test Topology Starting test: CutoffServers ......................... CHD1DOMINO1 passed test CutoffServers Starting test: NCSecDesc ......................... CHD1DOMINO1 passed test NCSecDesc Starting test: NetLogons ......................... CHD1DOMINO1 passed test NetLogons Starting test: Advertising ......................... CHD1DOMINO1 passed test Advertising Starting test: KnowsOfRoleHolders ......................... CHD1DOMINO1 passed test KnowsOfRoleHolders Starting test: RidManager ......................... CHD1DOMINO1 passed test RidManager Starting test: MachineAccount ......................... CHD1DOMINO1 passed test MachineAccount Starting test: Services ......................... CHD1DOMINO1 passed test Services Starting test: OutboundSecureChannels ** Did not run Outbound Secure Channels test because /testdomain: was not entered ......................... CHD1DOMINO1 passed test OutboundSecureChannels Starting test: ObjectsReplicated ......................... CHD1DOMINO1 passed test ObjectsReplicated Starting test: frssysvol ......................... CHD1DOMINO1 passed test frssysvol Starting test: frsevent ......................... CHD1DOMINO1 passed test frsevent Starting test: kccevent ......................... CHD1DOMINO1 passed test kccevent Starting test: systemlog ......................... CHD1DOMINO1 passed test systemlog Starting test: VerifyReplicas ......................... CHD1DOMINO1 passed test VerifyReplicas Starting test: VerifyReferences ......................... CHD1DOMINO1 passed test VerifyReferences Starting test: VerifyEnterpriseReferences The following problems were found while verifying various important DN references. Note, that these problems can be reported because of latency in replication. So follow up to resolve the following problems, only if the same problem is reported on all DCs for a given domain or if the problem persists after replication has had reasonable time to replicate changes. [1] Problem: Missing Expected Value Base Object: CN=VERNALIS-CKX7CN,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: frsComputerReference Value Object Description: "DC Account Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article: Q312862 [2] Problem: Missing Expected Value Base Object: CN=VERNALIS-CKX7CN,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: serverReference Value Object Description: "DSA Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article Q312862 [3] Problem: Missing Expected Value Base Object: CN=VERNALIS-SQL,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: frsComputerReference Value Object Description: "DC Account Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article: Q312862 [4] Problem: Missing Expected Value Base Object: CN=VERNALIS-SQL,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: serverReference Value Object Description: "DSA Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article Q312862 ......................... CHD1DOMINO1 failed test VerifyEnterpriseReferences Starting test: CheckSecurityError [CHD1DOMINO1] No security related replication errors were found on this DC! To target the connection to a specific source DC use /ReplSource:<DC>. ......................... CHD1DOMINO1 passed test CheckSecurityError DNS Tests are running and not hung. Please wait a few minutes... Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom 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 : vernalis Starting test: CrossRefValidation ......................... vernalis passed test CrossRefValidation Starting test: CheckSDRefDom ......................... vernalis passed test CheckSDRefDom Running enterprise tests on : vernalis.com Starting test: Intersite ......................... vernalis.com passed test Intersite Starting test: FsmoCheck ......................... vernalis.com passed test FsmoCheck Starting test: DNS Test results for domain controllers: DC: chd1domino1.vernalis.com Domain: vernalis.com TEST: Forwarders/Root hints (Forw) Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4) Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201) Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12) Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90) Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10) Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241) Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.36.4) Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53) Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17) Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30) Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129) Error: Root hints list has invalid root hint server: l.root-servers.net. (198.32.64.12) Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33) Summary of test results for DNS servers used by the above domain controllers: DNS server: 128.63.2.53 (h.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53 DNS server: 128.8.10.90 (d.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90 DNS server: 192.112.36.4 (g.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4 DNS server: 192.203.230.10 (e.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10 DNS server: 192.228.79.201 (b.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.228.79.201 DNS server: 192.33.4.12 (c.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12 DNS server: 192.36.148.17 (i.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17 DNS server: 192.5.5.241 (f.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241 DNS server: 192.58.128.30 (j.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.58.128.30 DNS server: 193.0.14.129 (k.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129 DNS server: 198.32.64.12 (l.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12 DNS server: 198.41.0.4 (a.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4 DNS server: 202.12.27.33 (m.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33 Summary of DNS test results: Auth Basc Forw Del Dyn RReg Ext ________________________________________________________________ Domain: vernalis.com chd1domino1 PASS PASS FAIL PASS PASS PASS n/a ......................... vernalis.com failed test DNS ################################################################################# Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\CHD1DOMINO2 Starting test: Connectivity ......................... CHD1DOMINO2 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\CHD1DOMINO2 Starting test: Replications [Replications Check,CHD1DOMINO2] Inbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_INBOUND_REPL" [Replications Check,CHD1DOMINO2] Outbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_OUTBOUND_REPL" ......................... CHD1DOMINO2 failed test Replications Starting test: Topology ......................... CHD1DOMINO2 passed test Topology Starting test: CutoffServers ......................... CHD1DOMINO2 passed test CutoffServers Starting test: NCSecDesc ......................... CHD1DOMINO2 passed test NCSecDesc Starting test: NetLogons ......................... CHD1DOMINO2 passed test NetLogons Starting test: Advertising Warning: DsGetDcName returned information for \\chd1domino1.vernalis.com, when we were trying to reach CHD1DOMINO2. Server is not responding or is not considered suitable. ......................... CHD1DOMINO2 failed test Advertising Starting test: KnowsOfRoleHolders ......................... CHD1DOMINO2 passed test KnowsOfRoleHolders Starting test: RidManager ......................... CHD1DOMINO2 passed test RidManager Starting test: MachineAccount ......................... CHD1DOMINO2 passed test MachineAccount Starting test: Services w32time Service is stopped on [CHD1DOMINO2] NETLOGON Service is paused on [CHD1DOMINO2] ......................... CHD1DOMINO2 failed test Services Starting test: OutboundSecureChannels ** Did not run Outbound Secure Channels test because /testdomain: was not entered ......................... CHD1DOMINO2 passed test OutboundSecureChannels Starting test: ObjectsReplicated ......................... CHD1DOMINO2 passed test ObjectsReplicated Starting test: frssysvol ......................... CHD1DOMINO2 passed test frssysvol Starting test: frsevent ......................... CHD1DOMINO2 passed test frsevent Starting test: kccevent ......................... CHD1DOMINO2 passed test kccevent Starting test: systemlog An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:26 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:14 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:15 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:16 (Event String could not be retrieved) ......................... CHD1DOMINO2 failed test systemlog Starting test: VerifyReplicas ......................... CHD1DOMINO2 passed test VerifyReplicas Starting test: VerifyReferences ......................... CHD1DOMINO2 passed test VerifyReferences Starting test: VerifyEnterpriseReferences The following problems were found while verifying various important DN references. Note, that these problems can be reported because of latency in replication. So follow up to resolve the following problems, only if the same problem is reported on all DCs for a given domain or if the problem persists after replication has had reasonable time to replicate changes. [1] Problem: Missing Expected Value Base Object: CN=VERNALIS-CKX7CN,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: frsComputerReference Value Object Description: "DC Account Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article: Q312862 [2] Problem: Missing Expected Value Base Object: CN=VERNALIS-CKX7CN,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: serverReference Value Object Description: "DSA Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article Q312862 [3] Problem: Missing Expected Value Base Object: CN=VERNALIS-SQL,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: frsComputerReference Value Object Description: "DC Account Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article: Q312862 [4] Problem: Missing Expected Value Base Object: CN=VERNALIS-SQL,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com Base Object Description: "SYSVOL FRS Member Object" Value Object Attribute Name: serverReference Value Object Description: "DSA Object" Recommended Action: Check if this server is deleted, and if so clean up this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article Q312862 ......................... CHD1DOMINO2 failed test VerifyEnterpriseReferences Starting test: CheckSecurityError [CHD1DOMINO2] No security related replication errors were found on this DC! To target the connection to a specific source DC use /ReplSource:<DC>. ......................... CHD1DOMINO2 passed test CheckSecurityError DNS Tests are running and not hung. Please wait a few minutes... Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom 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 : vernalis Starting test: CrossRefValidation ......................... vernalis passed test CrossRefValidation Starting test: CheckSDRefDom ......................... vernalis passed test CheckSDRefDom Running enterprise tests on : vernalis.com Starting test: Intersite ......................... vernalis.com passed test Intersite Starting test: FsmoCheck ......................... vernalis.com passed test FsmoCheck Starting test: DNS Test results for domain controllers: DC: chd1domino2.vernalis.com Domain: vernalis.com TEST: Basic (Basc) Error: NETLOGON service is not running TEST: Forwarders/Root hints (Forw) Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4) Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201) Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12) Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90) Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10) Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241) Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.36.4) Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53) Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17) Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30) Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129) Error: Root hints list has invalid root hint server: l.root-servers.net. (198.32.64.12) Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33) Summary of test results for DNS servers used by the above domain controllers: DNS server: 128.63.2.53 (h.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53 DNS server: 128.8.10.90 (d.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90 DNS server: 192.112.36.4 (g.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4 DNS server: 192.203.230.10 (e.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10 DNS server: 192.228.79.201 (b.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.228.79.201 DNS server: 192.33.4.12 (c.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12 DNS server: 192.36.148.17 (i.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17 DNS server: 192.5.5.241 (f.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241 DNS server: 192.58.128.30 (j.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.58.128.30 DNS server: 193.0.14.129 (k.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129 DNS server: 198.32.64.12 (l.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12 DNS server: 198.41.0.4 (a.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4 DNS server: 202.12.27.33 (m.root-servers.net.) 1 test failure on this DNS server This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33 Summary of DNS test results: Auth Basc Forw Del Dyn RReg Ext ________________________________________________________________ Domain: vernalis.com chd1domino2 PASS FAIL FAIL PASS PASS PASS n/a ......................... vernalis.com failed test DNS
Free Windows Admin Tool Kit Click here and download it now
February 22nd, 2010 9:18pm

Hi Meinolf Weber, I have posted DC1 dcdiag /d Command Line: "dcdiag.exe /d" Domain Controller Diagnosis Performing initial setup: * Verifying that the local machine chd1domino1, is a DC. * Connecting to directory service on server chd1domino1. chd1domino1.currentTime = 20100222174138.0Z chd1domino1.highestCommittedUSN = 9696311 chd1domino1.isSynchronized = 1 chd1domino1.isGlobalCatalogReady = 1 * Collecting site info. * Identifying all servers. CHD1DOMINO1.currentTime = 20100222174138.0Z CHD1DOMINO1.highestCommittedUSN = 9696311 CHD1DOMINO1.isSynchronized = 1 CHD1DOMINO1.isGlobalCatalogReady = 1 * Identifying all NC cross-refs. * Found 2 DC(s). Testing 1 of them. Done gathering initial info. ===============================================Printing out pDsInfo GLOBAL: ulNumServers=2 pszRootDomain=vernalis.com pszNC= pszRootDomainFQDN=DC=vernalis,DC=com pszConfigNc=CN=Configuration,DC=vernalis,DC=com pszPartitionsDn=CN=Partitions,CN=Configuration,DC=vernalis,DC=com iSiteOptions=0 dwTombstoneLifeTimeDays=60 dwForestBehaviorVersion=0 HomeServer=0, CHD1DOMINO1 SERVER: pServer[0].pszName=CHD1DOMINO1 pServer[0].pszGuidDNSName=32202f44-cd9b-4322-94b1-2d8486921250._msdcs.vernalis.com pServer[0].pszDNSName=chd1domino1.vernalis.com pServer[0].pszDn=CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pServer[0].pszComputerAccountDn=CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com pServer[0].uuidObjectGuid=32202f44-cd9b-4322-94b1-2d8486921250 pServer[0].uuidInvocationId=32202f44-cd9b-4322-94b1-2d8486921250 pServer[0].iSite=0 (Default-First-Site-Name) pServer[0].iOptions=1 pServer[0].ftLocalAcquireTime=48ec5be0 01cab3e6 pServer[0].ftRemoteConnectTime=48e07500 01cab3e6 pServer[0].ppszMasterNCs: ppszMasterNCs[0]=DC=ForestDnsZones,DC=vernalis,DC=com ppszMasterNCs[1]=DC=DomainDnsZones,DC=vernalis,DC=com ppszMasterNCs[2]=CN=Schema,CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[3]=CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[4]=DC=vernalis,DC=com SERVER: pServer[1].pszName=CHD1DOMINO2 pServer[1].pszGuidDNSName=c965921e-927d-4e64-b32c-b677fdf81c96._msdcs.vernalis.com pServer[1].pszDNSName=chd1domino2.vernalis.com pServer[1].pszDn=CN=NTDS Settings,CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pServer[1].pszComputerAccountDn=CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com pServer[1].uuidObjectGuid=c965921e-927d-4e64-b32c-b677fdf81c96 pServer[1].uuidInvocationId=60a515f0-d1cc-4bfb-b9e1-fd000105b417 pServer[1].iSite=0 (Default-First-Site-Name) pServer[1].iOptions=6 pServer[1].ftLocalAcquireTime=00000000 00000000 pServer[1].ftRemoteConnectTime=00000000 00000000 pServer[1].ppszMasterNCs: ppszMasterNCs[0]=DC=ForestDnsZones,DC=vernalis,DC=com ppszMasterNCs[1]=DC=DomainDnsZones,DC=vernalis,DC=com ppszMasterNCs[2]=CN=Schema,CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[3]=CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[4]=DC=vernalis,DC=com SITES: pSites[0].pszName=Default-First-Site-Name pSites[0].pszSiteSettings=CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pSites[0].pszISTG=CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pSites[0].iSiteOption=0 pSites[0].cServers=2 NC: pNCs[0].pszName=ForestDnsZones pNCs[0].pszDn=DC=ForestDnsZones,DC=vernalis,DC=com pNCs[0].aCrInfo[0].dwFlags=0x00000201 pNCs[0].aCrInfo[0].pszDn=CN=3706d5c1-9c91-40ac-9d4d-c2e1e2cc6eb9,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[0].aCrInfo[0].pszDnsRoot=ForestDnsZones.vernalis.com pNCs[0].aCrInfo[0].iSourceServer=0 pNCs[0].aCrInfo[0].pszSourceServer=(null) pNCs[0].aCrInfo[0].ulSystemFlags=0x00000005 pNCs[0].aCrInfo[0].bEnabled=TRUE pNCs[0].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[0].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[0].aCrInfo[0].pszNetBiosName=(null) pNCs[0].aCrInfo[0].cReplicas=-1 pNCs[0].aCrInfo[0].aszReplicas= NC: pNCs[1].pszName=DomainDnsZones pNCs[1].pszDn=DC=DomainDnsZones,DC=vernalis,DC=com pNCs[1].aCrInfo[0].dwFlags=0x00000201 pNCs[1].aCrInfo[0].pszDn=CN=3d06f132-05fa-484d-8466-0963cd345277,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[1].aCrInfo[0].pszDnsRoot=DomainDnsZones.vernalis.com pNCs[1].aCrInfo[0].iSourceServer=0 pNCs[1].aCrInfo[0].pszSourceServer=(null) pNCs[1].aCrInfo[0].ulSystemFlags=0x00000005 pNCs[1].aCrInfo[0].bEnabled=TRUE pNCs[1].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[1].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[1].aCrInfo[0].pszNetBiosName=(null) pNCs[1].aCrInfo[0].cReplicas=-1 pNCs[1].aCrInfo[0].aszReplicas= NC: pNCs[2].pszName=Schema pNCs[2].pszDn=CN=Schema,CN=Configuration,DC=vernalis,DC=com pNCs[2].aCrInfo[0].dwFlags=0x00000201 pNCs[2].aCrInfo[0].pszDn=CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[2].aCrInfo[0].pszDnsRoot=vernalis.com pNCs[2].aCrInfo[0].iSourceServer=0 pNCs[2].aCrInfo[0].pszSourceServer=(null) pNCs[2].aCrInfo[0].ulSystemFlags=0x00000001 pNCs[2].aCrInfo[0].bEnabled=TRUE pNCs[2].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[2].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[2].aCrInfo[0].pszNetBiosName=(null) pNCs[2].aCrInfo[0].cReplicas=-1 pNCs[2].aCrInfo[0].aszReplicas= NC: pNCs[3].pszName=Configuration pNCs[3].pszDn=CN=Configuration,DC=vernalis,DC=com pNCs[3].aCrInfo[0].dwFlags=0x00000201 pNCs[3].aCrInfo[0].pszDn=CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[3].aCrInfo[0].pszDnsRoot=vernalis.com pNCs[3].aCrInfo[0].iSourceServer=0 pNCs[3].aCrInfo[0].pszSourceServer=(null) pNCs[3].aCrInfo[0].ulSystemFlags=0x00000001 pNCs[3].aCrInfo[0].bEnabled=TRUE pNCs[3].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[3].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[3].aCrInfo[0].pszNetBiosName=(null) pNCs[3].aCrInfo[0].cReplicas=-1 pNCs[3].aCrInfo[0].aszReplicas= NC: pNCs[4].pszName=vernalis pNCs[4].pszDn=DC=vernalis,DC=com pNCs[4].aCrInfo[0].dwFlags=0x00000201 pNCs[4].aCrInfo[0].pszDn=CN=VERNALIS,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[4].aCrInfo[0].pszDnsRoot=vernalis.com pNCs[4].aCrInfo[0].iSourceServer=0 pNCs[4].aCrInfo[0].pszSourceServer=(null) pNCs[4].aCrInfo[0].ulSystemFlags=0x00000003 pNCs[4].aCrInfo[0].bEnabled=TRUE pNCs[4].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[4].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[4].aCrInfo[0].pszNetBiosName=(null) pNCs[4].aCrInfo[0].cReplicas=-1 pNCs[4].aCrInfo[0].aszReplicas= 5 NC TARGETS: ForestDnsZones, DomainDnsZones, Schema, Configuration, vernalis, 1 TARGETS: CHD1DOMINO1, =============================================Done Printing pDsInfo Doing initial required tests Testing server: Default-First-Site-Name\CHD1DOMINO1 Starting test: Connectivity * Active Directory LDAP Services Check Failure Analysis: CHD1DOMINO1 ... OK. * Active Directory RPC Services Check ......................... CHD1DOMINO1 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\CHD1DOMINO1 Starting test: Replications * Replications Check DC=ForestDnsZones,DC=vernalis,DC=com has 5 cursors. Skipping server CHD1DOMINO2, because it has outbound replication disabled DC=DomainDnsZones,DC=vernalis,DC=com has 5 cursors. Skipping server CHD1DOMINO2, because it has outbound replication disabled CN=Schema,CN=Configuration,DC=vernalis,DC=com has 6 cursors. Skipping server CHD1DOMINO2, because it has outbound replication disabled CN=Configuration,DC=vernalis,DC=com has 6 cursors. Skipping server CHD1DOMINO2, because it has outbound replication disabled DC=vernalis,DC=com has 6 cursors. Skipping server CHD1DOMINO2, because it has outbound replication disabled * Replication Latency Check DC=ForestDnsZones,DC=vernalis,DC=com Latency information for 3 entries in the vector were ignored. 3 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=DomainDnsZones,DC=vernalis,DC=com Latency information for 3 entries in the vector were ignored. 3 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). CN=Schema,CN=Configuration,DC=vernalis,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). CN=Configuration,DC=vernalis,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=vernalis,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). * Replication Site Latency Check Site Settings = CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com [0x904de,v=63029,t=2010-02-22 23:09:48,g=32202f44-cd9b-4322-94b1-2d8486921250,orig=9696309,local=9696309] Elapsed time (sec) = 110 ......................... CHD1DOMINO1 passed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions check for all NC's on DC CHD1DOMINO1. * Security Permissions Check for DC=ForestDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for DC=DomainDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for CN=Schema,CN=Configuration,DC=vernalis,DC=com (Schema,Version 2) * Security Permissions Check for CN=Configuration,DC=vernalis,DC=com (Configuration,Version 2) * Security Permissions Check for DC=vernalis,DC=com (Domain,Version 2) ......................... CHD1DOMINO1 passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\CHD1DOMINO1\netlogon Verified share \\CHD1DOMINO1\sysvol ......................... CHD1DOMINO1 passed test NetLogons Starting test: Advertising The DC CHD1DOMINO1 is advertising itself as a DC and having a DS. The DC CHD1DOMINO1 is advertising as an LDAP server The DC CHD1DOMINO1 is advertising as having a writeable directory The DC CHD1DOMINO1 is advertising as a Key Distribution Center The DC CHD1DOMINO1 is advertising as a time server The DS CHD1DOMINO1 is advertising as a GC. ......................... CHD1DOMINO1 passed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Domain Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role PDC Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Rid Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com ......................... CHD1DOMINO1 passed test KnowsOfRoleHolders Starting test: RidManager ridManagerReference = CN=RID Manager$,CN=System,DC=vernalis,DC=com * Available RID Pool for the Domain is 5106 to 1073741823 fSMORoleOwner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com * chd1domino1.vernalis.com is the RID Master * DsBind with RID Master was successful rIDSetReferences = CN=RID Set,CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com * rIDAllocationPool is 3606 to 4105 * rIDPreviousAllocationPool is 3606 to 4105 * rIDNextRID: 3834 ......................... CHD1DOMINO1 passed test RidManager Starting test: MachineAccount Checking machine account for DC CHD1DOMINO1 on DC CHD1DOMINO1. * SPN found :LDAP/chd1domino1.vernalis.com/vernalis.com * SPN found :LDAP/chd1domino1.vernalis.com * SPN found :LDAP/CHD1DOMINO1 * SPN found :LDAP/chd1domino1.vernalis.com/VERNALIS * SPN found :LDAP/32202f44-cd9b-4322-94b1-2d8486921250._msdcs.vernalis.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/32202f44-cd9b-4322-94b1-2d8486921250/vernalis.com * SPN found :HOST/chd1domino1.vernalis.com/vernalis.com * SPN found :HOST/chd1domino1.vernalis.com * SPN found :HOST/CHD1DOMINO1 * SPN found :HOST/chd1domino1.vernalis.com/VERNALIS * SPN found :GC/chd1domino1.vernalis.com/vernalis.com ......................... CHD1DOMINO1 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 ......................... CHD1DOMINO1 passed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated CHD1DOMINO1 is in domain DC=vernalis,DC=com Checking for CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com in domain DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com in domain CN=Configuration,DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. ......................... CHD1DOMINO1 passed test ObjectsReplicated Starting test: frssysvol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... CHD1DOMINO1 passed test frssysvol Starting test: frsevent * The File Replication Service Event log test ......................... CHD1DOMINO1 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. ......................... CHD1DOMINO1 passed test kccevent Starting test: systemlog * The System Event log test Found no errors in System Event log in the last 60 minutes. ......................... CHD1DOMINO1 passed test systemlog Test omitted by user request: VerifyReplicas Starting test: VerifyReferences The system object reference (serverReference) CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. The system object reference (frsComputerReferenceBL) CN=CHD1DATASERVER1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com are correct. The system object reference (serverReferenceBL) CN=CHD1DATASERVER1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. ......................... CHD1DOMINO1 passed test VerifyReferences Test omitted by user request: VerifyEnterpriseReferences Test omitted by user request: CheckSecurityError Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom 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 : vernalis Starting test: CrossRefValidation ......................... vernalis passed test CrossRefValidation Starting test: CheckSDRefDom ......................... vernalis passed test CheckSDRefDom Running enterprise tests on : vernalis.com Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. ......................... vernalis.com passed test Intersite Starting test: FsmoCheck GC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd PDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Preferred Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd KDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd ......................... vernalis.com passed test FsmoCheck Test omitted by user request: DNS Test omitted by user request: DNS
February 22nd, 2010 9:30pm

Hi Meinolf Weber, I have posted DC2 dcdiag /d Command Line: "dcdiag.exe /d" Domain Controller Diagnosis Performing initial setup: * Verifying that the local machine chd1domino2, is a DC. * Connecting to directory service on server chd1domino2. chd1domino2.currentTime = 20100222174554.0Z chd1domino2.highestCommittedUSN = 13033551 chd1domino2.isSynchronized = 1 chd1domino2.isGlobalCatalogReady = 0 * Collecting site info. * Identifying all servers. CHD1DOMINO2.currentTime = 20100222174554.0Z CHD1DOMINO2.highestCommittedUSN = 13033551 CHD1DOMINO2.isSynchronized = 1 CHD1DOMINO2.isGlobalCatalogReady = 0 * Identifying all NC cross-refs. * Found 2 DC(s). Testing 1 of them. Done gathering initial info. ===============================================Printing out pDsInfo GLOBAL: ulNumServers=2 pszRootDomain=vernalis.com pszNC= pszRootDomainFQDN=DC=vernalis,DC=com pszConfigNc=CN=Configuration,DC=vernalis,DC=com pszPartitionsDn=CN=Partitions,CN=Configuration,DC=vernalis,DC=com iSiteOptions=0 dwTombstoneLifeTimeDays=60 dwForestBehaviorVersion=0 HomeServer=1, CHD1DOMINO2 SERVER: pServer[0].pszName=CHD1DOMINO1 pServer[0].pszGuidDNSName=32202f44-cd9b-4322-94b1-2d8486921250._msdcs.vernalis.com pServer[0].pszDNSName=chd1domino1.vernalis.com pServer[0].pszDn=CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pServer[0].pszComputerAccountDn=CN=CHD1DOMINO1,OU=Domain Controllers,DC=vernalis,DC=com pServer[0].uuidObjectGuid=32202f44-cd9b-4322-94b1-2d8486921250 pServer[0].uuidInvocationId=32202f44-cd9b-4322-94b1-2d8486921250 pServer[0].iSite=0 (Default-First-Site-Name) pServer[0].iOptions=1 pServer[0].ftLocalAcquireTime=00000000 00000000 pServer[0].ftRemoteConnectTime=00000000 00000000 pServer[0].ppszMasterNCs: ppszMasterNCs[0]=DC=ForestDnsZones,DC=vernalis,DC=com ppszMasterNCs[1]=DC=DomainDnsZones,DC=vernalis,DC=com ppszMasterNCs[2]=CN=Schema,CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[3]=CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[4]=DC=vernalis,DC=com SERVER: pServer[1].pszName=CHD1DOMINO2 pServer[1].pszGuidDNSName=c965921e-927d-4e64-b32c-b677fdf81c96._msdcs.vernalis.com pServer[1].pszDNSName=chd1domino2.vernalis.com pServer[1].pszDn=CN=NTDS Settings,CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pServer[1].pszComputerAccountDn=CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com pServer[1].uuidObjectGuid=c965921e-927d-4e64-b32c-b677fdf81c96 pServer[1].uuidInvocationId=60a515f0-d1cc-4bfb-b9e1-fd000105b417 pServer[1].iSite=0 (Default-First-Site-Name) pServer[1].iOptions=6 pServer[1].ftLocalAcquireTime=e1a41f80 01cab3e6 pServer[1].ftRemoteConnectTime=e176f500 01cab3e6 pServer[1].ppszMasterNCs: ppszMasterNCs[0]=DC=ForestDnsZones,DC=vernalis,DC=com ppszMasterNCs[1]=DC=DomainDnsZones,DC=vernalis,DC=com ppszMasterNCs[2]=CN=Schema,CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[3]=CN=Configuration,DC=vernalis,DC=com ppszMasterNCs[4]=DC=vernalis,DC=com SITES: pSites[0].pszName=Default-First-Site-Name pSites[0].pszSiteSettings=CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pSites[0].pszISTG=CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com pSites[0].iSiteOption=0 pSites[0].cServers=2 NC: pNCs[0].pszName=ForestDnsZones pNCs[0].pszDn=DC=ForestDnsZones,DC=vernalis,DC=com pNCs[0].aCrInfo[0].dwFlags=0x00000201 pNCs[0].aCrInfo[0].pszDn=CN=3706d5c1-9c91-40ac-9d4d-c2e1e2cc6eb9,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[0].aCrInfo[0].pszDnsRoot=ForestDnsZones.vernalis.com pNCs[0].aCrInfo[0].iSourceServer=1 pNCs[0].aCrInfo[0].pszSourceServer=(null) pNCs[0].aCrInfo[0].ulSystemFlags=0x00000005 pNCs[0].aCrInfo[0].bEnabled=TRUE pNCs[0].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[0].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[0].aCrInfo[0].pszNetBiosName=(null) pNCs[0].aCrInfo[0].cReplicas=-1 pNCs[0].aCrInfo[0].aszReplicas= NC: pNCs[1].pszName=DomainDnsZones pNCs[1].pszDn=DC=DomainDnsZones,DC=vernalis,DC=com pNCs[1].aCrInfo[0].dwFlags=0x00000201 pNCs[1].aCrInfo[0].pszDn=CN=3d06f132-05fa-484d-8466-0963cd345277,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[1].aCrInfo[0].pszDnsRoot=DomainDnsZones.vernalis.com pNCs[1].aCrInfo[0].iSourceServer=1 pNCs[1].aCrInfo[0].pszSourceServer=(null) pNCs[1].aCrInfo[0].ulSystemFlags=0x00000005 pNCs[1].aCrInfo[0].bEnabled=TRUE pNCs[1].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[1].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[1].aCrInfo[0].pszNetBiosName=(null) pNCs[1].aCrInfo[0].cReplicas=-1 pNCs[1].aCrInfo[0].aszReplicas= NC: pNCs[2].pszName=Schema pNCs[2].pszDn=CN=Schema,CN=Configuration,DC=vernalis,DC=com pNCs[2].aCrInfo[0].dwFlags=0x00000201 pNCs[2].aCrInfo[0].pszDn=CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[2].aCrInfo[0].pszDnsRoot=vernalis.com pNCs[2].aCrInfo[0].iSourceServer=1 pNCs[2].aCrInfo[0].pszSourceServer=(null) pNCs[2].aCrInfo[0].ulSystemFlags=0x00000001 pNCs[2].aCrInfo[0].bEnabled=TRUE pNCs[2].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[2].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[2].aCrInfo[0].pszNetBiosName=(null) pNCs[2].aCrInfo[0].cReplicas=-1 pNCs[2].aCrInfo[0].aszReplicas= NC: pNCs[3].pszName=Configuration pNCs[3].pszDn=CN=Configuration,DC=vernalis,DC=com pNCs[3].aCrInfo[0].dwFlags=0x00000201 pNCs[3].aCrInfo[0].pszDn=CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[3].aCrInfo[0].pszDnsRoot=vernalis.com pNCs[3].aCrInfo[0].iSourceServer=1 pNCs[3].aCrInfo[0].pszSourceServer=(null) pNCs[3].aCrInfo[0].ulSystemFlags=0x00000001 pNCs[3].aCrInfo[0].bEnabled=TRUE pNCs[3].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[3].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[3].aCrInfo[0].pszNetBiosName=(null) pNCs[3].aCrInfo[0].cReplicas=-1 pNCs[3].aCrInfo[0].aszReplicas= NC: pNCs[4].pszName=vernalis pNCs[4].pszDn=DC=vernalis,DC=com pNCs[4].aCrInfo[0].dwFlags=0x00000201 pNCs[4].aCrInfo[0].pszDn=CN=VERNALIS,CN=Partitions,CN=Configuration,DC=vernalis,DC=com pNCs[4].aCrInfo[0].pszDnsRoot=vernalis.com pNCs[4].aCrInfo[0].iSourceServer=1 pNCs[4].aCrInfo[0].pszSourceServer=(null) pNCs[4].aCrInfo[0].ulSystemFlags=0x00000003 pNCs[4].aCrInfo[0].bEnabled=TRUE pNCs[4].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[4].aCrInfo[0].pszSDReferenceDomain=(null) pNCs[4].aCrInfo[0].pszNetBiosName=(null) pNCs[4].aCrInfo[0].cReplicas=-1 pNCs[4].aCrInfo[0].aszReplicas= 5 NC TARGETS: ForestDnsZones, DomainDnsZones, Schema, Configuration, vernalis, 1 TARGETS: CHD1DOMINO2, =============================================Done Printing pDsInfo Doing initial required tests Testing server: Default-First-Site-Name\CHD1DOMINO2 Starting test: Connectivity * Active Directory LDAP Services Check Failure Analysis: CHD1DOMINO2 ... OK. * Active Directory RPC Services Check ......................... CHD1DOMINO2 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\CHD1DOMINO2 Starting test: Replications * Replications Check [Replications Check,CHD1DOMINO2] Inbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_INBOUND_REPL" [Replications Check,CHD1DOMINO2] Outbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_OUTBOUND_REPL" ......................... CHD1DOMINO2 failed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions check for all NC's on DC CHD1DOMINO2. * Security Permissions Check for DC=ForestDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for DC=DomainDnsZones,DC=vernalis,DC=com (NDNC,Version 2) * Security Permissions Check for CN=Schema,CN=Configuration,DC=vernalis,DC=com (Schema,Version 2) * Security Permissions Check for CN=Configuration,DC=vernalis,DC=com (Configuration,Version 2) * Security Permissions Check for DC=vernalis,DC=com (Domain,Version 2) ......................... CHD1DOMINO2 passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\CHD1DOMINO2\netlogon Verified share \\CHD1DOMINO2\sysvol ......................... CHD1DOMINO2 passed test NetLogons Starting test: Advertising Warning: DsGetDcName returned information for \\chd1domino1.vernalis.com, when we were trying to reach CHD1DOMINO2. Server is not responding or is not considered suitable. The DC CHD1DOMINO2 is advertising itself as a DC and having a DS. The DC CHD1DOMINO2 is advertising as an LDAP server The DC CHD1DOMINO2 is advertising as having a writeable directory The DC CHD1DOMINO2 is advertising as a Key Distribution Center The DC CHD1DOMINO2 is advertising as a time server ......................... CHD1DOMINO2 failed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com CHD1DOMINO1.currentTime = 20100222174615.0Z CHD1DOMINO1.highestCommittedUSN = 9696355 CHD1DOMINO1.isSynchronized = 1 CHD1DOMINO1.isGlobalCatalogReady = 1 Role Domain Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role PDC Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Rid Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com ......................... CHD1DOMINO2 passed test KnowsOfRoleHolders Starting test: RidManager ridManagerReference = CN=RID Manager$,CN=System,DC=vernalis,DC=com * Available RID Pool for the Domain is 5106 to 1073741823 fSMORoleOwner = CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com * chd1domino1.vernalis.com is the RID Master * DsBind with RID Master was successful rIDSetReferences = CN=RID Set,CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com * rIDAllocationPool is 4606 to 5105 * rIDPreviousAllocationPool is 4106 to 4605 * rIDNextRID: 4401 ......................... CHD1DOMINO2 passed test RidManager Starting test: MachineAccount Checking machine account for DC CHD1DOMINO2 on DC CHD1DOMINO2. * SPN found :LDAP/chd1domino2.vernalis.com/vernalis.com * SPN found :LDAP/chd1domino2.vernalis.com * SPN found :LDAP/CHD1DOMINO2 * SPN found :LDAP/chd1domino2.vernalis.com/VERNALIS * SPN found :LDAP/c965921e-927d-4e64-b32c-b677fdf81c96._msdcs.vernalis.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/c965921e-927d-4e64-b32c-b677fdf81c96/vernalis.com * SPN found :HOST/chd1domino2.vernalis.com/vernalis.com * SPN found :HOST/chd1domino2.vernalis.com * SPN found :HOST/CHD1DOMINO2 * SPN found :HOST/chd1domino2.vernalis.com/VERNALIS * SPN found :GC/chd1domino2.vernalis.com/vernalis.com ......................... CHD1DOMINO2 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 w32time Service is stopped on [CHD1DOMINO2] * Checking Service: NETLOGON NETLOGON Service is paused on [CHD1DOMINO2] ......................... CHD1DOMINO2 failed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated CHD1DOMINO2 is in domain DC=vernalis,DC=com Checking for CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com in domain DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com in domain CN=Configuration,DC=vernalis,DC=com on 1 servers Object is up-to-date on all servers. ......................... CHD1DOMINO2 passed test ObjectsReplicated Starting test: frssysvol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... CHD1DOMINO2 passed test frssysvol Starting test: frsevent * The File Replication Service Event log test ......................... CHD1DOMINO2 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. ......................... CHD1DOMINO2 passed test kccevent Starting test: systemlog * The System Event log test An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:26 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 22:22:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:14 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:15 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 02/22/2010 23:15:16 (Event String could not be retrieved) ......................... CHD1DOMINO2 failed test systemlog Test omitted by user request: VerifyReplicas Starting test: VerifyReferences The system object reference (serverReference) CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. The system object reference (frsComputerReferenceBL) CN=CHD1DOMINO2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=CHD1DOMINO2,OU=Domain Controllers,DC=vernalis,DC=com are correct. The system object reference (serverReferenceBL) CN=CHD1DOMINO2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=vernalis,DC=com and backlink on CN=NTDS Settings,CN=CHD1DOMINO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com are correct. ......................... CHD1DOMINO2 passed test VerifyReferences Test omitted by user request: VerifyEnterpriseReferences Test omitted by user request: CheckSecurityError Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom 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 : vernalis Starting test: CrossRefValidation ......................... vernalis passed test CrossRefValidation Starting test: CheckSDRefDom ......................... vernalis passed test CheckSDRefDom Running enterprise tests on : vernalis.com Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. ......................... vernalis.com passed test Intersite Starting test: FsmoCheck GC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd PDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd Preferred Time Server Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd KDC Name: \\chd1domino1.vernalis.com Locator Flags: 0xe00003fd ......................... vernalis.com passed test FsmoCheck Test omitted by user request: DNS Test omitted by user request: DNS
Free Windows Admin Tool Kit Click here and download it now
February 22nd, 2010 9:32pm

Hi Meinolf Weber, We have posted some Directory Service Error Log for your reference. Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1308 Date: 2/22/2010 Time: 3:58:20 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: CHD1DOMINO2 Description: The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed. Attempts: 226 Domain controller: CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Period of time (minutes): 129 The Connection object for this domain controller will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this domain controller resumes, the temporary connection will be removed. Additional Data Error value: 8457 The destination server is currently rejecting replication requests. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ############################################################################### Event Type: Error Event Source: NTDS Replication Event Category: Replication Event ID: 1863 Date: 2/21/2010 Time: 7:38:06 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: CHD1DOMINO2 Description: This is the replication status for the following directory partition on the local domain controller. Directory partition: DC=ForestDnsZones,DC=vernalis,DC=com The local domain controller has not received replication information from a number of domain controllers within the configured latency interval. Latency Interval (Hours): 24 Number of domain controllers in all sites: 1 Number of domain controllers in this site: 1 The latency interval can be modified with the following registry key. Registry Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours) To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ###################################################################### Event Type: Error Event Source: NTDS Replication Event Category: Replication Event ID: 1863 Date: 2/21/2010 Time: 7:38:06 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: CHD1DOMINO2 Description: This is the replication status for the following directory partition on the local domain controller. Directory partition: DC=DomainDnsZones,DC=vernalis,DC=com The local domain controller has not received replication information from a number of domain controllers within the configured latency interval. Latency Interval (Hours): 24 Number of domain controllers in all sites: 1 Number of domain controllers in this site: 1 The latency interval can be modified with the following registry key. Registry Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours) To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ######################################################################## Event Type: Error Event Source: NTDS Replication Event Category: Replication Event ID: 1863 Date: 2/21/2010 Time: 7:38:06 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: CHD1DOMINO2 Description: This is the replication status for the following directory partition on the local domain controller. Directory partition: CN=Schema,CN=Configuration,DC=vernalis,DC=com The local domain controller has not received replication information from a number of domain controllers within the configured latency interval. Latency Interval (Hours): 24 Number of domain controllers in all sites: 1 Number of domain controllers in this site: 1 The latency interval can be modified with the following registry key. Registry Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours) To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ####################################################################### Event Type: Warning Event Source: NTDS Replication Event Category: Replication Event ID: 2093 Date: 2/21/2010 Time: 7:38:06 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: CHD1DOMINO2 Description: The remote server which is the owner of a FSMO role is not responding. This server has not replicated with the FSMO role owner recently. Operations which require contacting a FSMO operation master will fail until this condition is corrected. FSMO Role: CN=Schema,CN=Configuration,DC=vernalis,DC=com FSMO Server DN: CN=NTDS Settings,CN=CHD1DOMINO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=vernalis,DC=com Latency threshold (hours): 24 Elapsed time since last successful replication (hours): 34 User Action: This server has not replicated successfully with the FSMO role holder server. 1. The FSMO role holder server may be down or not responding. Please address the problem with this server. 2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com. 3. If the FSMO role holder server used to be a domain controller, but was not demoted successfully, then the objects representing that server are still in the forest. This can occur if a domain controller has its operating system reinstalled or if a forced removal is performed. These lingering state objects should be removed using the NTDSUTIL.EXE metadata cleanup function. 4. The FSMO role holder may not be a direct replication partner. If it is an indirect or transitive partner, then there are one or more intermediate replication partners through which replication data must flow. The total end to end replication latency should be smaller than the replication latency threshold, or else this warning may be reported prematurely. 5. Replication is blocked somewhere along the path of servers between the FSMO role holder server and this server. Consult your forest topology plan to determine the likely route for replication between these servers. Check the status of replication using repadmin /showrepl at each of these servers. The following operations may be impacted: Schema: You will no longer be able to modify the schema for this forest. Domain Naming: You will no longer be able to add or remove domains from this forest. PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory accounts. RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups. Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ########################################################################### Event Type: Error Event Source: NTDS Replication Event Category: Replication Event ID: 1863 Date: 2/21/2010 Time: 7:38:06 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: CHD1DOMINO2 Description: This is the replication status for the following directory partition on the local domain controller. Directory partition: CN=Configuration,DC=vernalis,DC=com The local domain controller has not received replication information from a number of domain controllers within the configured latency interval. Latency Interval (Hours): 24 Number of domain controllers in all sites: 1 Number of domain controllers in this site: 1 The latency interval can be modified with the following registry key. Registry Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours) To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
February 22nd, 2010 9:35pm

Hi, Rich Crandall I have posted DC1 and DC2 net share DC1 Share name Resource Remark ------------------------------------------------------------------------------- IPC$ Remote IPC ADMIN$ C:\WINDOWS Remote Admin D$ D:\ Default share E$ E:\ Default share C$ C:\ Default share NETLOGON D:\WINDOWS\SYSVOL\sysvol\vernalis.com\SCRIPTS Logon server share SYSVOL D:\WINDOWS\SYSVOL\sysvol Logon server share The command completed successfully. DC2 Share name Resource Remark ------------------------------------------------------------------------------- IPC$ Remote IPC ADMIN$ C:\WINDOWS Remote Admin D$ D:\ Default share C$ C:\ Default share BlackBerry Enterprise Server D:\Program Files\Research In Motion\BlackBerry Enterprise Server NETLOGON C:\WINDOWS\SYSVOL\sysvol\vernalis.com\SCRIPTS Logon server share SYSVOL C:\WINDOWS\SYSVOL\sysvol Logon server share The command completed successfully.
Free Windows Admin Tool Kit Click here and download it now
February 22nd, 2010 9:38pm

Hello,did you follow this article asmentioned in the dcdiag output:http://support.microsoft.com/kb/312862Also see this for starting with all event viewer entries:http://technet.microsoft.com/en-us/library/cc738415(WS.10).aspxExpand the + in the left pabe to see all related information for the event id's.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
February 23rd, 2010 10:59am

Hi Meinolf Weber, Iam able to view only the error log in Directory Services Event Log. Remaining File replication are good. Could you advice me without depromote solve the issue. Thanks Alagar.
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2010 2:45pm

Hello,please post an unedited repadmin /showrepl from each DC here. From my point of view you have to demote the problem DC and run metadata cleanup to get it fixed correct.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
February 23rd, 2010 3:06pm

Hello, We have post repadmin /showrepl of DC1 and DC2. Iam confused which one is affected. chd1domino1 or chd1domino2 ? C:\>repadmin /showrepl repadmin running command /showrepl against server localhost Default-First-Site-Name\CHD1DOMINO2 DC Options: DISABLE_INBOUND_REPL DISABLE_OUTBOUND_REPL Site Options: (none) DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 DC invocationID: 60a515f0-d1cc-4bfb-b9e1-fd000105b417 ==== INBOUND NEIGHBORS ====================================== DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-23 18:05:41 failed, result 8457 (0x2109): The destination server is currently rejecting replication requests. 930 consecutive failure(s). Last success @ 2010-02-22 23:16:03. CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-23 17:54:47 failed, result 8457 (0x2109): The destination server is currently rejecting replication requests. 46 consecutive failure(s). Last success @ 2010-02-22 23:16:03. CN=Schema,CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-23 17:23:18 failed, result 8457 (0x2109): The destination server is currently rejecting replication requests. 19 consecutive failure(s). Last success @ 2010-02-22 23:16:02. DC=DomainDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-23 17:23:18 failed, result 8457 (0x2109): The destination server is currently rejecting replication requests. 19 consecutive failure(s). Last success @ 2010-02-22 23:16:02. DC=ForestDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-23 17:26:27 failed, result 8457 (0x2109): The destination server is currently rejecting replication requests. 29 consecutive failure(s). Last success @ 2010-02-22 23:16:02. Source: Default-First-Site-Name\CHD1DOMINO1 ******* 911 CONSECUTIVE FAILURES since 2010-02-22 23:16:03 Last error: 8457 (0x2109): The destination server is currently rejecting replication requests. ############################################################################################# repadmin running command /showrepl against server localhost Default-First-Site-Name\CHD1DOMINO1 DC Options: IS_GC Site Options: (none) DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 DC invocationID: 32202f44-cd9b-4322-94b1-2d8486921250 ==== INBOUND NEIGHBORS ====================================== DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-23 18:13:05 failed, result 8456 (0x2108): The source server is currently rejecting replication requests. 46 consecutive failure(s). Last success @ 2010-02-22 23:16:24. CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-23 17:29:03 failed, result 8456 (0x2108): The source server is currently rejecting replication requests. 45 consecutive failure(s). Last success @ 2010-02-22 23:16:24. CN=Schema,CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-23 17:19:40 failed, result 8456 (0x2108): The source server is currently rejecting replication requests. 19 consecutive failure(s). Last success @ 2010-02-22 23:16:23. DC=DomainDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-23 17:45:16 failed, result 8456 (0x2108): The source server is currently rejecting replication requests. 51 consecutive failure(s). Last success @ 2010-02-22 23:16:23. DC=ForestDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-23 17:19:41 failed, result 8456 (0x2108): The source server is currently rejecting replication requests. 22 consecutive failure(s). Last success @ 2010-02-22 23:16:23. Source: Default-First-Site-Name\CHD1DOMINO2 ******* 51 CONSECUTIVE FAILURES since 2010-02-22 23:16:24 Last error: 8456 (0x2108): The source server is currently rejecting replication requests.
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2010 3:47pm

Hello,please correct your replication settings as shown in one of the first output's you have posted on CHD1DOMINO2:[Replications Check,CHD1DOMINO2] Inbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_INBOUND_REPL" [Replications Check,CHD1DOMINO2] Outbound replication is disabled. To correct, run "repadmin /options CHD1DOMINO2 -DISABLE_OUTBOUND_REPL"Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
February 23rd, 2010 3:53pm

Hi Meinorlf Weber, Great Excellent Thanks for your valuable time and effort. Now its working good. Thanks again. Thanks Alagar. Now DC1 and DC2 replicate good. C:\>repadmin /showrepl repadmin running command /showrepl against server localhost Default-First-Site-Name\CHD1DOMINO2 DC Options: (none) Site Options: (none) DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 DC invocationID: 60a515f0-d1cc-4bfb-b9e1-fd000105b417 ==== INBOUND NEIGHBORS ====================================== DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-24 10:45:44 was successful. CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-24 10:44:01 was successful. CN=Schema,CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-24 10:23:19 was successful. DC=DomainDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-24 10:45:37 was successful. DC=ForestDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO1 via RPC DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 Last attempt @ 2010-02-24 10:30:16 was successful. C:\>repadmin /showrepl repadmin running command /showrepl against server localhost Default-First-Site-Name\CHD1DOMINO1 DC Options: IS_GC Site Options: (none) DC object GUID: 32202f44-cd9b-4322-94b1-2d8486921250 DC invocationID: 32202f44-cd9b-4322-94b1-2d8486921250 ==== INBOUND NEIGHBORS ====================================== DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-24 10:45:10 was successful. CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-24 10:44:08 was successful. CN=Schema,CN=Configuration,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-24 10:19:41 was successful. DC=DomainDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-24 10:45:43 was successful. DC=ForestDnsZones,DC=vernalis,DC=com Default-First-Site-Name\CHD1DOMINO2 via RPC DC object GUID: c965921e-927d-4e64-b32c-b677fdf81c96 Last attempt @ 2010-02-24 10:30:22 was successful. C:\>
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2010 8:28am

Hello,nice to hear that you found it.:-)Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
February 24th, 2010 3:17pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics