I had this question after viewing Windows 2012 DC replication issue
-I recently took over a new customer. They have a single DC on Server 2012 R2. Joining a windows client to the domain seems normal. But after a few hours...a few days, the client cannot authenticate as a domain member even with cached information. (sorry, I don't have the specific error message).
-The client looks like a domain member, but in Local Users and Groups, the computer appears to have fallen off the domain with only the SIDS showing instead of domain usernames\groups.
-The server event log looks like a disaster. It appears that the server was originally named Temp and then named DC2. However, DNS and AD still points at Temp.
1925 The attempt to establish a replication link for the following writable directory partition failed.
4 The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server dc2$.
47 Time Provider NtpClient: No valid response has been received from manually configured peer pool.ntp.org after 8 attempts to contact it.
Ran Repadmin with results attached.Repadmin.rtf
The server CoastTemp does not exist. However, the IP is listed in DNS.
Your expertise is greatly appreciated. I am thinking a domain rebuild is in order. But, there are 40 clients and the cust will not want to pay the expense of a rebuild because they don't understand that they have problems. Some of you will tell me to drop the customer :)