What to do with a server after tombstone date past ?
Hello
We are getting errors Source: Ntfrs Event ID: 13508 and 13509.
In the errors there are three different servers being specified that have lost cross-relationship, ServerA/ServerB/ServerC and I get the 13508 on all three servers. So we are getting different 13508 errors for each, on each.
From these i can't tell which has fallen out of sync from the domain.
All the AD objects we've added users, computers etc are still replicating properly and we havent' had any LDAP services halt. So we're confused as to the severity of this - let alone what should be done.
HERE'S THE ERROR IN FULL WRITTING
The File Replication Service is having trouble enabling replication from ServerA to ServerB 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.
[1] FRS can not correctly resolve the DNS name ServerA.domain.local from this computer.
[2] FRS is not running on ServerA.domain.local.
[3] The topology information in the Active Directory 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.
For more information, see Help and Support Center at
We are getting errors Source: Ntfrs Event ID: 13508 and 13509.
In the errors there are three different servers being specified that have lost cross-relationship, ServerA/ServerB/ServerC and I get the 13508 on all three servers. So we are getting different 13508 errors for each, on each.
From these i can't tell which has fallen out of sync from the domain.
All the AD objects we've added users, computers etc are still replicating properly and we havent' had any LDAP services halt. So we're confused as to the severity of this - let alone what should be done.
HERE'S THE ERROR IN FULL WRITTING
The File Replication Service is having trouble enabling replication from ServerA to ServerB 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.
[1] FRS can not correctly resolve the DNS name ServerA.domain.local from this computer.
[2] FRS is not running on ServerA.domain.local.
[3] The topology information in the Active Directory 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.
For more information, see Help and Support Center at
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER