File Replication Service - NtFrs - Error messages - Not broken but not good either
The File Replication Service is having trouble enabling replication from ServerB to ServerA for c:\windows\sysvol\domain using the DNS name ServerA.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning.  FRS can not correctly resolve the DNS name ServerB.domain.local from this computer.  FRS is not running on ServerB.domain.local.  The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
1 - I've confirmed that the servers are able to resolve via DNS.
2 - I've confirmed that FRS is running on all servers involved.
3 - I'm not certain where to check for this.
So this is just a nagging error that I'm seeing on a server, and I want to get it resolved. Can anyone provide any pointers?
scottalanmiller last edited by
What is the bandwidth and latency between those machines? Are they over a WAN?
These are both on the same LAN.
1GB connection on each server, ServerB is a VM on Hyper-V. The host also has 1GB connection.
Latency ranges from <1ms to 4ms, each way.