Dear all,
I have the following topology:
Two domain controllers (windows server 2008 r2 ) and one cas/hub server and one mailbox server
We have to shut down the primary domain controllers for physical maintenance but before doing this I transferred the masters roles to the additional one ,then shutdown the domain controller but due to a failure in the hard disk of the domain controller I made a bare metal recovery then made a dcdiag and I found the following errors
please advuce
WIN-I1H2NPJ9ASV failed test DFSREventStarting test: DFSREvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... WIN-I1H2NPJ9ASV failed test DFSREvent
Starting test: SysVolCheck
......................... WIN-I1H2NPJ9ASV passed test SysVolCheck
......................... WIN-I1H2NPJ9ASV passed test
ObjectsReplicated
Starting test: Replications
[Replications Check,WIN-I1H2NPJ9ASV] A recent replication attempt
failed:
From DC2 to WIN-I1H2NPJ9ASV
Naming Context: DC=DomainDnsZones,DC=marg,DC=local
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2019-07-26 13:57:17.
The last success occurred at 2019-07-25 11:48:53.
2 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC2
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,WIN-I1H2NPJ9ASV] A recent replication attempt
failed:
From DC2 to WIN-I1H2NPJ9ASV
Naming Context: CN=Schema,CN=Configuration,DC=marg,DC=local
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2019-07-26 13:54:43.
The last success occurred at 2019-07-25 11:48:53.
2 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Replications Check,WIN-I1H2NPJ9ASV] A recent replication attempt
failed:
From DC2 to WIN-I1H2NPJ9ASV
Naming Context: CN=Configuration,DC=marg,DC=local
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2019-07-26 13:53:26.
The last success occurred at 2019-07-26 13:45:55.
1 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Replications Check,WIN-I1H2NPJ9ASV] A recent replication attempt
failed:
From DC2 to WIN-I1H2NPJ9ASV
Naming Context: DC=marg,DC=local
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2019-07-26 13:56:00.
The last success occurred at 2019-07-25 11:49:12.
2 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC2
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
......................... WIN-I1H2NPJ9ASV failed test Replications
Starting test: RidManager
The DS has corrupt data: rIDPreviousAllocationPool value is not valid
No rids allocated -- please check eventlog.
The name "MARG :1b" could not be registered on the interface with IP address 172.16.5.157. The computer with the IP address 172.16.5.128 did not allow the name to be claimed by this computer.
An error event occurred. EventID: 0xC00010E1
Time Generated: 07/26/2019 13:39:25
The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
A warning event occurred. EventID: 0x0000000C
Time Generated: 07/26/2019 13:39:46
Event String:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source,
but it is the AD PDC emulator for the domain at the root of the forest,
so there is no machine above it in the domain hierarchy to use as a time source.
It is recommended that you either configure a reliable time service in the root domain,
or manually configure the AD PDC to synchronize with an external time source.
Otherwise, this machine will function as the authoritative time source in the domain hierarchy.
If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
Time Generated: 07/26/2019 13:46:09
Event String:
The name "MARG :1b" could not be registered on the interface with IP address 172.16.5.157. The computer with the IP address 172.16.5.128 did not allow the name to be claimed by this computer.
An error event occurred. EventID: 0xC00010E1
Time Generated: 07/26/2019 13:46:21
Event String:
A warning event occurred. EventID: 0x000003F6