Devin
asked on
DCdiag is failing SystemLog with public DNS
I am finally getting back to trying to migrate a 2012 DC to 2016. SYSVOL/NETLOGON is not replicating and DCDiag is showing errors.
DCdiag is failing SystemLog showing the new AD server as well 4 entries for public google DNS. I have checked both DC's nic settings of which they point to themselves else the other DC. There is no reference to a public DNS from either DC. I checked DNS on both servers and neither have records for 8.8.8.8 or 8.8.4.4
Out of a last ditch effort I ran ipconfig /flushdns and dnscmd /clearcache in hopes of resolving this but the problem remains.
I am still receiving an FrsEvent in DCDiag which i was attempting to use FRSDiag to figure out why. It fails repeatedly with NTFRSUTL ERROR - Cannot RPC to computer, mydc; 000006d9 (1753)... Make sure you are logged on as a Domain Admin! Skipping!
The user is the domain admin and I have tried other users with domain/enterprise admin roles with the same result.
This is the DCDiag output
This is the FRSDiag output
DCdiag is failing SystemLog showing the new AD server as well 4 entries for public google DNS. I have checked both DC's nic settings of which they point to themselves else the other DC. There is no reference to a public DNS from either DC. I checked DNS on both servers and neither have records for 8.8.8.8 or 8.8.4.4
Out of a last ditch effort I ran ipconfig /flushdns and dnscmd /clearcache in hopes of resolving this but the problem remains.
I am still receiving an FrsEvent in DCDiag which i was attempting to use FRSDiag to figure out why. It fails repeatedly with NTFRSUTL ERROR - Cannot RPC to computer, mydc; 000006d9 (1753)... Make sure you are logged on as a Domain Admin! Skipping!
The user is the domain admin and I have tried other users with domain/enterprise admin roles with the same result.
This is the DCDiag output
C:\Windows\system32>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = MyDC
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\MyDC
Starting test: Connectivity
......................... MyDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\MyDC
Starting test: Advertising
......................... MyDC passed test Advertising
Starting test: FrsEvent
......................... MyDC passed test FrsEvent
Starting 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.
......................... MyDC passed test DFSREvent
Starting test: SysVolCheck
......................... MyDC passed test SysVolCheck
Starting test: KccEvent
......................... MyDC passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... MyDC passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... MyDC passed test MachineAccount
Starting test: NCSecDesc
......................... MyDC passed test NCSecDesc
Starting test: NetLogons
......................... MyDC passed test NetLogons
Starting test: ObjectsReplicated
......................... MyDC passed test ObjectsReplicated
Starting test: Replications
......................... MyDC passed test Replications
Starting test: RidManager
......................... MyDC passed test RidManager
Starting test: Services
......................... MyDC passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x0000272C
Time Generated: 01/26/2019 10:46:28
Event String:
DCOM was unable to communicate with the computer 200.1.1.8 using any
of the configured protocols; requested by PID 17d4 (C:\Windows\system32\dcd
iag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 01/26/2019 10:47:01
Event String:
DCOM was unable to communicate with the computer 8.8.4.4 using any o
f the configured protocols; requested by PID 17d4 (C:\Windows\system32\dcdia
g.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 01/26/2019 10:47:22
Event String:
DCOM was unable to communicate with the computer 8.8.8.8 using any o
f the configured protocols; requested by PID 17d4 (C:\Windows\system32\dcdia
g.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 01/26/2019 11:29:41
Event String:
DCOM was unable to communicate with the computer 8.8.4.4 using any o
f the configured protocols; requested by PID 156c (C:\Windows\system32\dcdia
g.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 01/26/2019 11:30:02
Event String:
DCOM was unable to communicate with the computer 8.8.8.8 using any o
f the configured protocols; requested by PID 156c (C:\Windows\system32\dcdia
g.exe).
......................... MyDC failed test SystemLog
Starting test: VerifyReferences
......................... MyDC passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : MyDomain
Starting test: CheckSDRefDom
......................... MyDomain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... MyDomain passed test CrossRefValidation
Running enterprise tests on : MyDomain.local
Starting test: LocatorCheck
......................... MyDomain.local passed test LocatorCheck
Starting test: Intersite
......................... MyDomain.local passed test Intersite
C:\Windows\system32>ping 200.1.1.8
Pinging 200.1.1.8 with 32 bytes of data:
Reply from 200.1.1.8: bytes=32 time=1ms TTL=128
Reply from 200.1.1.8: bytes=32 time=1ms TTL=128
Ping statistics for 200.1.1.8:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Control-C
^C
C:\Windows\system32>This is the FRSDiag output
------------------------------------------------------------
FRSDiag v1.7 on 1/26/2019 10:57:46 AM
.\MyDC on 2019-01-26 at 10.57.46 AM
------------------------------------------------------------
Checking for errors in Directory Service Event Log ....
NTDS General 1/26/2019 2:00:35 AM Error 2087 Active Directory Domain Services could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory Domain Services from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources. Source domain controller: MyDC2016 Failing DNS host name: 9b00d50c-4fda-4d28-a71b-a34f14675276._msdcs.MyDomain.local NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1: Registry Path: HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client User Action: 1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498. 2) Confirm that the source domain controller is running Active Directory Domain Services and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>". 3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns dcdiag /test:dns 4) Verify that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows: dcdiag /test:dns 5) For further analysis of DNS error failures see KB 824449: http://support.microsoft.com/?kbid=824449 Additional Data Error value: 11001 No such host is known.
NTDS Replication 1/23/2019 4:25:19 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/23/2019 4:25:19 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/23/2019 4:25:19 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/23/2019 4:25:19 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/23/2019 4:25:19 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/22/2019 4:25:17 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/22/2019 4:25:17 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/22/2019 4:25:17 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/22/2019 4:25:17 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/22/2019 4:25:17 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/21/2019 4:25:15 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/21/2019 4:25:15 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/21/2019 4:25:15 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/21/2019 4:25:15 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/21/2019 4:25:15 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/20/2019 4:25:14 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/20/2019 4:25:14 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/20/2019 4:25:14 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/20/2019 4:25:14 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/20/2019 4:25:14 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/19/2019 4:25:12 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/19/2019 4:25:12 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/19/2019 4:25:12 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/19/2019 4:25:12 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/19/2019 4:25:12 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/18/2019 4:25:10 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/18/2019 4:25:10 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/18/2019 4:25:10 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/18/2019 4:25:10 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/18/2019 4:25:10 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/17/2019 4:25:09 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/17/2019 4:25:09 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/17/2019 4:25:09 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/17/2019 4:25:09 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/17/2019 4:25:09 PM Error 1864 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/16/2019 4:25:07 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/16/2019 4:25:07 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/16/2019 4:25:07 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/16/2019 4:25:07 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/16/2019 4:25:07 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/15/2019 4:25:05 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/15/2019 4:25:05 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/15/2019 4:25:05 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/15/2019 4:25:05 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/15/2019 4:25:05 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/14/2019 4:25:03 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/14/2019 4:25:03 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=DomainDnsZones,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/14/2019 4:25:03 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Schema,CN=Configuration,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/14/2019 4:25:03 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
NTDS Replication 1/14/2019 4:25:03 PM Error 1863 This is the replication status for the following directory partition on this directory server. Directory partition: DC=MyDomain,DC=local This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers 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 directory servers by name, use the dcdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
WARNING: Found Directory Service Errors in the past 15 days! FRS Depends on AD so Check AD Replication!
......... failed 51
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... could not check!
Checking for Replica Set configuration triggers... could not check!
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)...could not check!
Checking for suspicious inlog entries ...could not check!
Checking for suspicious outlog entries ...could not check!
Checking for appropriate staging area size ...could not check!
Checking NtFrs Service (and dependent services) state...
ERROR : Required Service not Running : "File Replication" is currently "Stopped"
......... failed 1
Checking NtFrs related Registry Keys for possible problems...passed
Checking Repadmin Showreps for errors...
DC=MyDomain,DC=local
Default-First-Site-Name\MyDC2016 via RPC
objectGuid: 9b00d50c-4fda-4d28-a71b-a34f14675276
Last attempt @ 2019-01-26 10:45.04 failed, result 1722:
The RPC server is unavailable.
Last success @ 2019-01-26 09:18.57.
3 consecutive failure(s).
CN=Configuration,DC=MyDomain,DC=local
Default-First-Site-Name\MyDC2016 via RPC
objectGuid: 9b00d50c-4fda-4d28-a71b-a34f14675276
Last attempt @ 2019-01-26 10:43.40 failed, result 1722:
The RPC server is unavailable.
Last success @ 2019-01-26 09:10.51.
3 consecutive failure(s).
CN=Schema,CN=Configuration,DC=MyDomain,DC=local
Default-First-Site-Name\MyDC2016 via RPC
objectGuid: 9b00d50c-4fda-4d28-a71b-a34f14675276
Last attempt @ 2019-01-26 10:42.16 failed, result 1722:
The RPC server is unavailable.
Last success @ 2019-01-26 09:10.48.
3 consecutive failure(s).
DC=DomainDnsZones,DC=MyDomain,DC=local
Default-First-Site-Name\MyDC2016 via RPC
objectGuid: 9b00d50c-4fda-4d28-a71b-a34f14675276
Last attempt @ 2019-01-26 10:40.52 failed, result 1722:
The RPC server is unavailable.
Last success @ 2019-01-26 09:19.08.
3 consecutive failure(s).
DC=ForestDnsZones,DC=MyDomain,DC=local
Default-First-Site-Name\MyDC2016 via RPC
objectGuid: 9b00d50c-4fda-4d28-a71b-a34f14675276
Last attempt @ 2019-01-26 10:39.28 failed, result 1722:
The RPC server is unavailable.
Last success @ 2019-01-26 09:17.57.
3 consecutive failure(s).
......... failed 5
Final Result = Could not grab data
Rule of thumb:
1. On DCs, ensure the primary DNS is pointing to itself and secondary to a different DC (in the old days, this was not recommending due to DNS island issues but does not apply to Windows server 2008 or higher)
2. Do not use Internet routable IP address on the inside network (stick to a range in 10.0.0.0/8 range, i.e. 10.128.10.0/24 which gives you 254 usable IP addresses)
3. All client PCs should be pointing to DCs for DNS IP addresses
4. Use a .local zone or if you are going to use a real domain (i.e. presence on the Internet, then to ensure to use a sub-domain (i.e. business is called abcwidgets.com then use ad.abcwidgets.com or xyz.abcwidgets.com
5. Avoid using a domain name which has presence on the Internet as you will be faced with split DNS issues
Based on this, you should be able to find out what the issue is and if you provide more information then we could assist.
1. On DCs, ensure the primary DNS is pointing to itself and secondary to a different DC (in the old days, this was not recommending due to DNS island issues but does not apply to Windows server 2008 or higher)
2. Do not use Internet routable IP address on the inside network (stick to a range in 10.0.0.0/8 range, i.e. 10.128.10.0/24 which gives you 254 usable IP addresses)
3. All client PCs should be pointing to DCs for DNS IP addresses
4. Use a .local zone or if you are going to use a real domain (i.e. presence on the Internet, then to ensure to use a sub-domain (i.e. business is called abcwidgets.com then use ad.abcwidgets.com or xyz.abcwidgets.com
5. Avoid using a domain name which has presence on the Internet as you will be faced with split DNS issues
Based on this, you should be able to find out what the issue is and if you provide more information then we could assist.
Are you sure that your DCs are even using FRS to replicate SYSVOL? DFSR has been the preferred mechanism for SYSVOL replication since Windows Server 2008, but if your domain has been around since the pre-2008 days, it could still be using FRS. There's an easy way to tell: run dfsrmig /getglobalstate on one of the domain controllers. Post the output here, if you don't mind.
Wouldn't want to dive down an FRS rabbit hole when it's not even in use!
Wouldn't want to dive down an FRS rabbit hole when it's not even in use!
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
This might seem like bit of a stretch, but have to start somewhere....
Your AD Integrated DNS.... Where is it "Forwarding"?
Are you leveraging "Split-DNS" where your domain.com is used both internal and external.
What happens when you perform nslookup against your domain.com versus a ping?
Regarding the Default-First...
What happens when you open DNS administration and go to the NS records?
There are a couple of house cleaning issues relative to upgrades.
First, check Sites and Services to make sure all the Subnets for the network are represented.
The ones most concerned about are those Subnets where the IP networks are in different locations and you have Domain Controllers.
Sites and Services relative to Subnets needs to be correct.
Next, DNS and Reverse lookup Zones. Do they match Subnets in Sites and Services are do you have "typos".
Specifically, subnet addresses in Subnets in the SItes and Services and what locations they are associated.
Then, in DNS, do you have "leftover" Name Server records where all your DC's might have new names but the old records remain?
Remove them....
If you can confirm the "basics" then I'll move to next steps.
Last but not least? Is there are reason why the FRS services is stopped?
Required Service not Running : "File Replication" is currently "Stopped"
Bad GPO? Oversight?