Re: Replication Problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

Paul, here is Stihlse1's dcdiag /v /c /e log

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine stihlse1, is a DC.
* Connecting to directory service on server stihlse1.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 2 of them.
Done gathering initial info.

Doing initial required tests
Testing server: Default-First-Site-Name\STIHLSE1
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... STIHLSE1 passed test Connectivity

Testing server: Default-First-Site-Name\STIHLSE3
Starting test: Connectivity
* Active Directory LDAP Services Check
[STIHLSE3] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
***Error: The machine, STIHLSE3 could not be contacted, because of a

bad net response. Check to make sure that this machine is a Domain

Controller.
......................... STIHLSE3 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\STIHLSE1
Starting test: Replications
* Replications Check
[Replications Check,STIHLSE1] A recent replication attempt failed:
From STIHLSE3 to STIHLSE1
Naming Context: CN=Schema,CN=Configuration,DC=stihlse,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-03-09 11:19:14.
The last success occurred at 2006-02-21 14:49:33.
374 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,STIHLSE1] A recent replication attempt failed:
From STIHLSE3 to STIHLSE1
Naming Context: CN=Configuration,DC=stihlse,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-03-09 11:19:57.
The last success occurred at 2006-02-21 14:49:33.
435 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,STIHLSE1] A recent replication attempt failed:
From STIHLSE3 to STIHLSE1
Naming Context: DC=stihlse,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-03-09 11:20:39.
The last success occurred at 2006-03-09 07:54:44.
16 failures have occurred since the last success.
The source remains down. Please check the machine.
* Replication Latency Check
DC=ForestDnsZones,DC=stihlse,DC=com
Latency information for 1 entries in the vector were ignored.
1 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=stihlse,DC=com
Latency information for 1 entries in the vector were ignored.
1 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-RECEIVED LATENCY WARNING
STIHLSE1: Current time is 2006-03-09 11:22:16.
CN=Schema,CN=Configuration,DC=stihlse,DC=com
Last replication recieved from STIHLSE3 at 2006-02-21 14:49:33.
Latency information for 2 entries in the vector were ignored.
2 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=stihlse,DC=com
Last replication recieved from STIHLSE3 at 2006-02-21 14:49:33.
Latency information for 2 entries in the vector were ignored.
2 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=stihlse,DC=com
Latency information for 2 entries in the vector were ignored.
2 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).
......................... STIHLSE1 passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for
DC=ForestDnsZones,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
DC=DomainDnsZones,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
CN=Schema,CN=Configuration,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
CN=Configuration,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... STIHLSE1 passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for
DC=ForestDnsZones,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
DC=DomainDnsZones,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
CN=Schema,CN=Configuration,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
CN=Configuration,DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
DC=stihlse,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... STIHLSE1 passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC STIHLSE1.
* Security Permissions Check for
DC=ForestDnsZones,DC=stihlse,DC=com
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=stihlse,DC=com
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=stihlse,DC=com
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=stihlse,DC=com
(Configuration,Version 2)
* Security Permissions Check for
DC=stihlse,DC=com
(Domain,Version 2)
......................... STIHLSE1 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\STIHLSE1\netlogon
Verified share \\STIHLSE1\sysvol
......................... STIHLSE1 passed test NetLogons
Starting test: Advertising
The DC STIHLSE1 is advertising itself as a DC and having a DS.
The DC STIHLSE1 is advertising as an LDAP server
The DC STIHLSE1 is advertising as having a writeable directory
The DC STIHLSE1 is advertising as a Key Distribution Center
The DC STIHLSE1 is advertising as a time server
The DS STIHLSE1 is advertising as a GC.
......................... STIHLSE1 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com
Role Domain Owner = CN=NTDS
Settings,CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com
Role PDC Owner = CN=NTDS
Settings,CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com
Role Rid Owner = CN=NTDS
Settings,CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com
......................... STIHLSE1 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 3277 to 1073741823
* stihlse1.stihlse.com is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1777 to 2276
* rIDPreviousAllocationPool is 1777 to 2276
* rIDNextRID: 1816
......................... STIHLSE1 passed test RidManager
Starting test: MachineAccount
Checking machine account for DC STIHLSE1 on DC STIHLSE1.
* SPN found :LDAP/stihlse1.stihlse.com/stihlse.com
* SPN found :LDAP/stihlse1.stihlse.com
* SPN found :LDAP/STIHLSE1
* SPN found :LDAP/stihlse1.stihlse.com/STIHL
* SPN found
:LDAP/30bc8f2c-2038-485a-aad6-0eadc22d5e1e._msdcs.stihlse.com
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/30bc8f2c-2038-485a-aad6-0eadc22d5e1e/stihlse.com
* SPN found :HOST/stihlse1.stihlse.com/stihlse.com
* SPN found :HOST/stihlse1.stihlse.com
* SPN found :HOST/STIHLSE1
* SPN found :HOST/stihlse1.stihlse.com/STIHL
* SPN found :GC/stihlse1.stihlse.com/stihlse.com
......................... STIHLSE1 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
......................... STIHLSE1 passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
......................... STIHLSE1 passed test OutboundSecureChannels
Starting test: ObjectsReplicated
STIHLSE1 is in domain DC=stihlse,DC=com
Checking for CN=STIHLSE1,OU=Domain Controllers,DC=stihlse,DC=com in
domain DC=stihlse,DC=com on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com
in domain CN=Configuration,DC=stihlse,DC=com on 1 servers
Object is up-to-date on all servers.
......................... STIHLSE1 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... STIHLSE1 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... STIHLSE1 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.
......................... STIHLSE1 passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x00000457
Time Generated: 03/09/2006 11:00:00
Event String: Driver Amyuni PDF Converter 2.07 required for

printer Intuit Internal Printer is unknown.

Contact the administrator to install the driver

before you log in again.
An Error Event occured. EventID: 0x00000457
Time Generated: 03/09/2006 11:00:02
Event String: Driver hp LaserJet 1300 PCL 6 required for

printer !!joe!hplaser is unknown. Contact the

administrator to install the driver before you

log in again.
......................... STIHLSE1 failed test systemlog
Starting test: VerifyReplicas
......................... STIHLSE1 passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=STIHLSE1,OU=Domain Controllers,DC=stihlse,DC=com and backlink on


CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com

are correct.
The system object reference (frsComputerReferenceBL)

CN=STIHLSE1,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=stihlse,DC=com

and backlink on CN=STIHLSE1,OU=Domain Controllers,DC=stihlse,DC=com

are correct.
The system object reference (serverReferenceBL)

CN=STIHLSE1,CN=Domain System Volume (SYSVOL share),CN=File
Replication Service,CN=System,DC=stihlse,DC=com

and backlink on

CN=NTDS
Settings,CN=STIHLSE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=stihlse,DC=com

are correct.
......................... STIHLSE1 passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
......................... STIHLSE1 passed test
VerifyEnterpriseReferences
Starting test: CheckSecurityError
* Dr Auth: Beginning security errors check!
Found KDC STIHLSE1 for domain stihlse.com in site
Default-First-Site-Name
Checking machine account for DC STIHLSE1 on DC STIHLSE1.
* SPN found :LDAP/stihlse1.stihlse.com/stihlse.com
* SPN found :LDAP/stihlse1.stihlse.com
* SPN found :LDAP/STIHLSE1
* SPN found :LDAP/stihlse1.stihlse.com/STIHL
* SPN found
:LDAP/30bc8f2c-2038-485a-aad6-0eadc22d5e1e._msdcs.stihlse.com
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/30bc8f2c-2038-485a-aad6-0eadc22d5e1e/stihlse.com
* SPN found :HOST/stihlse1.stihlse.com/stihlse.com
* SPN found :HOST/stihlse1.stihlse.com
* SPN found :HOST/STIHLSE1
* SPN found :HOST/stihlse1.stihlse.com/STIHL
* SPN found :GC/stihlse1.stihlse.com/stihlse.com
Source DC STIHLSE3 has possible security error (1722). Diagnosing...
Found KDC STIHLSE1 for domain stihlse.com in site
Default-First-Site-Name
Checking time skew between servers:
STIHLSE3
STIHLSE1
Time is in sync: 0 seconds different.
Checking machine account for DC STIHLSE3 on DC STIHLSE1.
* SPN found :LDAP/stihlse3.stihlse.com/stihlse.com
* SPN found :LDAP/stihlse3.stihlse.com
* SPN found :LDAP/STIHLSE3
* SPN found :LDAP/stihlse3.stihlse.com/STIHL
* SPN found
:LDAP/d2955723-7b9a-4bf5-911b-8b09b1094d8a._msdcs.stihlse.com
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/d2955723-7b9a-4bf5-911b-8b09b1094d8a/stihlse.com
* SPN found :HOST/stihlse3.stihlse.com/stihlse.com
* SPN found :HOST/stihlse3.stihlse.com
* SPN found :HOST/STIHLSE3
* SPN found :HOST/stihlse3.stihlse.com/STIHL
* SPN found :GC/stihlse3.stihlse.com/stihlse.com
Checking for CN=STIHLSE3,OU=Domain
Controllers,DC=stihlse,DC=com in domain DC=stihlse,DC=com on 1 servers
Object is up-to-date on all servers.
* Security Permissions check for all NC's on DC STIHLSE3.
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=stihlse,DC=com
* Security Permissions Check for
CN=Configuration,DC=stihlse,DC=com
* Security Permissions Check for
DC=stihlse,DC=com
Ignoring DC STIHLSE3 in the convergence test of object
CN=STIHLSE1,OU=Domain Controllers,DC=stihlse,DC=com, because we cannot
connect!
Checking for CN=STIHLSE1,OU=Domain Controllers,DC=stihlse,DC=com in
domain DC=stihlse,DC=com on 1 servers
Object is up-to-date on all servers.
......................... STIHLSE1 failed test CheckSecurityError

Testing server: Default-First-Site-Name\STIHLSE3
Skipping all tests, because server STIHLSE3 is
not responding to directory service requests

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 : stihlse
Starting test: CrossRefValidation
......................... stihlse passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... stihlse passed test CheckSDRefDom

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

provided by the command line arguments provided.
......................... stihlse.com passed test Intersite
Starting test: FsmoCheck
GC Name: \\stihlse1.stihlse.com
Locator Flags: 0xe00003fd
PDC Name: \\stihlse1.stihlse.com
Locator Flags: 0xe00003fd
Time Server Name: \\stihlse1.stihlse.com
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\stihlse1.stihlse.com
Locator Flags: 0xe00003fd
KDC Name: \\stihlse1.stihlse.com
Locator Flags: 0xe00003fd
......................... stihlse.com passed test FsmoCheck
Starting test: DNS
Test results for domain controllers:

DC: stihlse3.stihlse.com
Domain: stihlse.com


TEST: Authentication (Auth)
Authentication test: Successfully completed

TEST: Basic (Basc)
Error: No LDAP connectivity
Error: No WMI connectivity
[Error details: 0x800706ba (Type: HRESULT - Facility:
Win32, Description: The RPC server is unavailable.) - Connection to WMI
server failed]


DC: stihlse1.stihlse.com
Domain: stihlse.com


TEST: Authentication (Auth)
Authentication test: Successfully completed

TEST: Basic (Basc)
Microsoft(R) Windows(R) Server 2003, Standard Edition
(Service Pack level: 0.0) is supported
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000001] HP NC7781 Gigabit Server Adapter:
MAC address is 00:0B:CD:E5:A5:4D
IP address is static
IP address: 10.0.1.2
DNS servers:
10.0.1.2 (<name unavailable>) [Valid]
The A record for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found
(primary)
Root zone on this DC/DNS server was not found

TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders Information:
204.117.214.10 (<name unavailable>) [Valid]

TEST: Delegations (Del)
No delegations were found in this zone on this DNS server

TEST: Dynamic update (Dyn)
Dynamic update is enabled on the zone stihlse.com.
Test record _dcdiag_test_record added successfully in zone
stihlse.com.
Test record _dcdiag_test_record deleted successfully in
zone stihlse.com.

TEST: Records registration (RReg)
Network Adapter [00000001] HP NC7781 Gigabit Server Adapter:
Matching A record found at DNS server 10.0.1.2:
stihlse1.stihlse.com

Matching CNAME record found at DNS server 10.0.1.2:
30bc8f2c-2038-485a-aad6-0eadc22d5e1e._msdcs.stihlse.com

Matching DC SRV record found at DNS server 10.0.1.2:
_ldap._tcp.dc._msdcs.stihlse.com

Matching GC SRV record found at DNS server 10.0.1.2:
_ldap._tcp.gc._msdcs.stihlse.com

Matching PDC SRV record found at DNS server 10.0.1.2:
_ldap._tcp.pdc._msdcs.stihlse.com


Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 10.0.1.2 (<name unavailable>)
All tests passed on this DNS server
This is a valid DNS server.
Name resolution is funtional. _ldap._tcp SRV record for the
forest root domain is registered

DNS server: 204.117.214.10 (<name unavailable>)
All tests passed on this DNS server
This is a valid DNS server.

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg
Ext

________________________________________________________________
Domain: stihlse.com
stihlse3 PASS FAIL n/a n/a n/a n/a
n/a
stihlse1 PASS PASS PASS PASS PASS PASS
n/a

......................... stihlse.com failed test DNS

.

Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Error after pdc rebuild
    ... "Failing SYSVOL replication problems may cause Group Policy problems". ... Connecting to directory service on server highfield-pdc01. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Replication fails with RPC error
    ... Verifying that the local machine Laguna, ... Connecting to directory service on server Laguna. ... The replication generated an error: ... Performing upstream analysis. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Replication fails with RPC error
    ... Connecting to directory service on server tahoe. ... Replication Site Latency Check ... Performing upstream analysis. ... Performing downstream (of target) analysis. ...
    (microsoft.public.windows.server.active_directory)
  • RE: KRB_APP_ERR_MODIFIED
    ... After that make sure that your replication between the two existing ... After that check that all entries form the server ... Performing upstream analysis. ... Performing downstream (of target) analysis. ...
    (microsoft.public.windows.server.active_directory)