James wrote:
Thanks again:
I ran netDiag with the /fix option, no errors were found. And I also
ran dcDiag for a second time and both are listed below. I can ping any
domain controller from any place across the WAN. Our firewalls do not
block any ports across our WAN.
DC Diag:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Acct\NT3
Starting test: Connectivity
......................... NT3 passed test Connectivity
Doing primary tests
Testing server: Acct\NT3
Starting test: Replications
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: DC=Acct,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 15:59.28.
The last success occurred at 2007-03-04 07:47.16.
438 failures have occurred since the last success.
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: CN=Schema,CN=Configuration,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 15:59.28.
The last success occurred at 2007-03-04 07:47.16.
438 failures have occurred since the last success.
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: CN=Configuration,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 15:59.28.
The last success occurred at 2007-03-04 07:47.16.
438 failures have occurred since the last success.
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: DC=pottsville,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 15:59.29.
The last success occurred at 2007-03-04 07:47.16.
438 failures have occurred since the last success.
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: DC=kenosha,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 15:59.29.
The last success occurred at 2007-03-04 07:47.16.
438 failures have occurred since the last success.
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: DC=lansing,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 15:59.28.
The last success occurred at 2007-03-04 07:47.16.
438 failures have occurred since the last success.
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: DC=chicago,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 15:59.28.
The last success occurred at 2007-03-04 07:47.16.
438 failures have occurred since the last success.
[Replications Check,NT3] A recent replication attempt failed:
From NT1 to NT3
Naming Context: DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 16:27.23.
The last success occurred at 2007-03-04 07:47.16.
457 failures have occurred since the last success.
......................... NT3 passed test Replications
Starting test: NCSecDesc
......................... NT3 passed test NCSecDesc
Starting test: NetLogons
......................... NT3 passed test NetLogons
Starting test: Advertising
......................... NT3 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... NT3 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... NT3 passed test RidManager
Starting test: MachineAccount
......................... NT3 passed test MachineAccount
Starting test: Services
......................... NT3 passed test Services
Starting test: ObjectsReplicated
......................... NT3 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... NT3 passed test frssysvol
Starting test: kccevent
......................... NT3 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000168F
Time Generated: 03/22/2007 16:14:47
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000168F
Time Generated: 03/22/2007 16:16:00
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000168F
Time Generated: 03/22/2007 16:16:02
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000168F
Time Generated: 03/22/2007 16:16:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000168F
Time Generated: 03/22/2007 16:16:09
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000452
Time Generated: 03/22/2007 16:16:47
Event String: The printer could not be installed.
......................... NT3 failed test systemlog
Running enterprise tests on : Corp.local
Starting test: Intersite
......................... Corp.local passed test Intersite
Starting test: FsmoCheck
......................... Corp.local passed test FsmoCheck
Net Diag
Thanks for the quick reply. These two DC's have been running fine
until 2 weeks ago.
I ran dcdiag and the only errors I see are
So you are failing replication whether you force it or not. But it
doesn't look like you included the entire DCDiag.
Try checking DNS (NetDiag /fix might help on all DCs); time (the real
time not the display time since we just did that DST thing), and
firewalls
or filters that might be preventing communication between DCs.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Corp\NT1
Starting test: Connectivity
......................... NT1 passed test Connectivity
Doing primary tests
Testing server: acct\NT1
Starting test: Replications
[Replications Check,NT1] A recent replication attempt failed:
From NT3 to NT1
Naming Context: DC=Acct,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 13:50.30.
The last success occurred at 2007-03-04 06:52.20.
419 failures have occurred since the last success.
[Replications Check,NT1] A recent replication attempt failed:
From NT3 to NT1
Naming Context: CN=Schema,CN=Configuration,DC=Corp,DC=local
The replication generated an error (5):
Access is denied.
The failure occurred at 2007-03-22 13:50.30.
The last success occurred at 2007-03-04 06:52.20.
419 failures have occurred since the last success.
Hello,
Currently I have 2 DC under one child domain. Whenever I try to
replicate either server's AD using "AD sites and services" I get
the
following
error:
"The following error has occurred during the attempt to synchronize
the domain controllers access is denied"
DNS server is running normally. Both servers are on the same LAN.
Both are Windows 2000 SP4 servers. Thank you in advance.
Are you using Terminal Services to reach the computer where you run
the AD Sites and Services MMC? Sometimes there are issues with that.
Do these DCs replicate normally?
Check with a complete "DCDiag /c" and search for FAIL or WARN
messages
by saving the output to a file.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
As Herb suggested, it is uncanny that this happened right at the DST
thing. "net time" on both DCs shows identical times?
...kurt