Forum Discussion
Solved
FRS 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 w...
The last thing I did was update the network from private to domain. I can't imagine that resolving it,
Yes, that would do it. The domain firewall profile would allow these ports to flow freely.
Configure firewall for AD domain and trusts - Windows Server | Microsoft Docs
I'd check these ports are flowing between networks.
Configure firewall for AD domain and trusts - Windows Server | Microsoft Docs
Thanks for the reply. I will give these a look. I used AngryPort scanner from DC to DC and it responds to both, but these may illuminate something I am missing.
As to doing the nonauthoritative restore do these steps on the receiving end. (hopefully its not tombstoned)
Use BurFlags to reinitialize File Replication Service (FRS) - Windows Server | Microsoft Docs
Any progress or updates? Please don't forget to close up thread by marking helpful replies.
Sounds good, let us know.
With one exception, it doesn't look to me portqry has anything that matters is filtered? Results are attached. Sorry about the docx.
One query causes it to crash each time and portqry throws an error.
portqry.exe -n dc2 -e 137 -p UDP exits with return code 0x80000003.Is the nonauthoritative restore how I can 'force' it to sync?
