Windows Server 2012 Active Directory Trust Relationship Problem

You use to get the error message “The security Database on the server does not have a computer account for this workstation trust relationship.” or shows “Login ID or password incorrect” while the time of logon on Windows Server 2012 R2, most recommended solution is re-join toActive Directory Domains or rebuild the server to fix the issue, before doing re-join/rebuild just make sure all the configuration like SPN (ServicePrincipalName), UPN (UserPrincipalName) are correctly configured, will discuss in detail with steps

Also Read: How to troubleshoot workstation Trust relationship issues on Domain

Will get the error like below while the time of Domain Login

How to check UserPrincipalName and DNSHostName

Go To Run
Type ADSIEDIT.msc
Browse to the computer object
Click Properties
Check the UserPrincipalName and DNSHostName Value
UserPrincipalName should be computername@Domainname(computer1@windowstricks.in)
DNSHostName should be computername.domainname (computer1.windowstricks.in)
Correct the value if require

Also Read: Domain Account unable to log-in with cached credentials on Windows 10

How to check the ServicePrincipalName

Open CMD
Type below command setspn –l computername (setspn –l computer1)
You should get below result
- HOST/computer1
  HOST/computer1.windowstricks.in
Correct the value if require

Also Read: Shortcut Keys for Windows server 2012 and 2012 R2

If the affected servers are on VM

Check the Time and time sync issue on affected servers, If servers are hosted on VM’s then disable time sync on vmware, so that all client will sync their time from domain PDC, check my previous article Can my hyper-v server be a Windows Time Server?

Also Read: Differences between Windows Server 2012 R2 Hyper-V and Hyper-V Server 2012 R2

Also Try this

Issue may be with NETBIOS Name on Domain name, try to rejoin back to Domain using NETBIOS Nam(domain), unlike the Domain FQDN (domain.com) while joining the affected server to Domain

If any of above solution fixing the issue, re-join the affected server back to Domain and also try to rebuild the server to fix the issue

Also Read: Active Directory Features in Windows Server 2012