frs
1 TopicFRS not replicating Event 13508, NtFrs
Two weeks ago our host went down for DC1. Since DC1, and DC2 are not replicating to one another. It is currently FRS. I discovered this while looking in to migrating to DFS. I have found and went through this: https://social.technet.microsoft.com/Forums/en-US/889ee624-1e6e-4e0d-a8b8-8d8a974ac0dc/2-new-dc-not-replicating-event-13508-ntfrs, but I don't know if a D2/D4 is what I need here. I have reviewed this as well: https://docs.microsoft.com/en-US/troubleshoot/windows-server/networking/use-burflags-to-reinitialize-frs. In this it doesn't specify which DC I set the flag on. I assume PDC, but either way from the bottom of the document this isn't going to fix my root cause issue. "If you configure an FRS member to complete an authoritative or nonauthoritative restore by using the BurFlags registry subkey, you don't resolve the issues that initially caused the replication problem." Other articles I have reviewed: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727056(v=technet.10)?redirectedfrom=MSDN https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727057(v=technet.10) I can ping from each device, and outputs for troubleshooting is below. I have confirmed ports for RPC are open and they can talk to one another over the network on 135. Services on both DCs are running as well. These are ran from DC1 PS C:\Users\administrator> ntfrsutl version dc2 NtFrsApi Version Information NtFrsApi Major : 0 NtFrsApi Minor : 0 NtFrsApi Compiled on: Aug 21 2013 16:23:00 NtFrs Version Information NtFrs Major : 0 NtFrs Minor : 0 NtFrs Compiled on : Aug 21 2013 16:23:00 Latest changes: Install Override fix OS Version 6.3 (9600) - SP (0.0) SM: 0x0110 PT: 0x02 Processor: AMD64 Level: 0x0006 Revision: 0x5507 Processor num/mask: 4/0000000f PS C:\Users\administrator> repadmin /showreps location1\DC1 DSA Options: IS_GC Site Options: (none) DSA object GUID: bd9d7382-7bd6-453e-9829-e898d8d84725 DSA invocationID: 47916ea1-707b-4c1f-902d-19e84aa68a98 ==== INBOUND NEIGHBORS ====================================== dc=mine,DC=com location2\dc2 via RPC DSA object GUID: 87eb9ba0-9358-4dd3-a30b-57f3ee78cfa2 Last attempt @ 2022-06-03 11:52:28 was successful. CN=Configuration,dc=mine,DC=com location2\dc2 via RPC DSA object GUID: 87eb9ba0-9358-4dd3-a30b-57f3ee78cfa2 Last attempt @ 2022-06-03 11:46:25 was successful. CN=Schema,CN=Configuration,dc=mine,DC=com location2\dc2 via RPC DSA object GUID: 87eb9ba0-9358-4dd3-a30b-57f3ee78cfa2 Last attempt @ 2022-06-03 11:46:25 was successful. DC=DomainDnsZones,dc=mine,DC=com location2\dc2 via RPC DSA object GUID: 87eb9ba0-9358-4dd3-a30b-57f3ee78cfa2 Last attempt @ 2022-06-03 11:46:25 was successful. DC=ForestDnsZones,dc=mine,DC=com location2\dc2 via RPC DSA object GUID: 87eb9ba0-9358-4dd3-a30b-57f3ee78cfa2 Last attempt @ 2022-06-03 11:46:25 was successful. Side question as well, how can I initiate/force an FRS sync? The log shows the failures once daily, 25 hours apart (one hour later each day) since the host went down, so I assumed it was a scheduled task, but I couldn't find anything in taskschd or a schedule option via ntfrsutl. Thanks!Solved11KViews1like12Comments
