2 servers loosing contact with domain controller Kerbos errors

Hi we have a client with mixed OS versions.

DC = Server 2012 r2
App server = Server 2008 r2
RDS = Server 2012 r2

DC migrated from 2003 to 2012 r2

Guide followed : Link


I have tryed many solutions to the problem but nothing has solved the issue. Since we are getting Kerberos messages i tried the standard to synch time servers. But to no help. Only thing that fixes the problem temporarily is rebooting the server.

Some of the errors are :

The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description.

Select allOpen in new window

Additional information : ID:4, SOURCE:Microsoft-Windows-Security-Kerberos
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server dc$. The target name used was ldap/DC.XXX.local. This indicates that the target server failed to decrypt the ticket provided by the client. 
This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. 
This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. 
Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (XXX.LOCAL) is different from the client domain (XXX.LOCAL), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

Select allOpen in new window

Additional information : ID:5719, SOURCE:NETLOGON
This computer was not able to set up a secure session with a domain controller in domain XXXdue to the following: 
There are currently no logon servers available to service the logon request. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. 

Select allOpen in new window

 Regards
Bjørn.