Hi guys.
I have found a problem on my network and I have tried to figure out how to fix it, but no success so far.
I have two domains, the first one is my main domain and the second one is my homologation domain.
My homologation domain trusts my main domain, but my main domain doesn't trust my homologation domain (non transitive trust).
Since beginning of November if anyone tries to change the password using Ctrl + Alt + Del and tries to change it of the other domain account, we get the error message below:
"The security database on the server does not have a computer account for this workstation trust relationship"
But this is quite weird because it changes the password successfully, but we get the error message.
Note: It just happens when I try to change the password from one domain to the second one.
For example: If I am logged on DOMAIN1 and I try to change password of an account on DOMAIN2, it changes successfully, but I get this error. It also happens if I try from DOMAIN2 to DOMAIN1, it changes, but error message.
Note2: Changing the password on the same domain that I am logged on, the problem doesn't happen.
Note3: When the problem started to happen we were installing and configuring ADFS (Federation Services) and Exchange Server (on different servers than Domain Controllers) on the homologation domain. Although we don't believe this is the problem.
Environment:
Main Domain: Domain Controllers running Windows Server 2012 R2 and Windows Server 2008 R2 (some branches, the headquarter is running 2012);
Homologation Domain: Domain Controllers running Windows Server 2012 R2 only;
Functional Level: Windows Server 2008 R2.
Client computer: Windows 8.1 (but even trying to change from any other computer the same problem happens).
What we've done trying to fix so far:
1. Uninstall ADFS (just in case);
2. Check Exchange configuration looking for some thing or issue about authentication;
3. Check for duplicates SPN (setspn -F -X);
4. Recreate the trust relationship (the same way than before);
5. Move FSMO between the servers;
6. Check DNS;
7. Reboot the servers (Domain Controllers);
8. DCDiag (no problems found);
9. Event Viewer of the domain controllers (nothing apparently related to the problem);
10. Rejoin the client to domain;
11. Check the workstation Event Viewer (just in case).
I don't know where is the problem exactly. We've researching for this since beginning of November and no success so far. :-(
Thank you in advance!
JC