How to fix “The security database on the server does not have a computer account for this workstation trust relationship. [ERROR_NO_TRUST_SAM_ACCOUNT (0x6FB)]” – Error Code 1787

Overview

In this article, we’ll focus on resolving the issue described as: “The security database on the server does not have a computer account for this workstation trust relationship. [ERROR_NO_TRUST_SAM_ACCOUNT (0x6FB)]”. This error, identified by the error code Error Code 1787, can impede your system’s performance, and here’s how you can fix it.

Identifying the Problem

Error Code 1787 arises when a workstation attempts to join a domain but the domain controller does not have a computer account for the workstation in its Security Accounts Manager (SAM) database. This error typically occurs in environments where the workstation was previously removed from the domain or when a new workstation is being added to the domain.

Common Fixes

1. Verify Domain Controller Connectivity:
– Ensure that the workstation can communicate with the domain controller.
– Ping the domain controller’s IP address or hostname.
– Check network connections and firewalls.

2. Recreate Computer Account:
– On the workstation, open an elevated command prompt.
– Run the command: netdom resetpwd /s:<domain_name> /ud:<domain_username> /pd:<domain_password>

3. Check Group Policy:
– Verify that the “Allow workstations to join domain” policy is enabled in the Group Policy settings of the domain.

Advanced Troubleshooting

1. Reset the Netlogon Service:
– Stop the Netlogon service on the workstation.
– Delete the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
– Start the Netlogon service.

2. Rebuild the Security Database:
– Boot the workstation into Directory Services Restore Mode.
– Run the command: ntdsutil /db recover
– Answer “yes” to all prompts.

Conclusion

Error Code 1787 can be resolved using the solutions outlined above. By following the steps carefully, you can restore your workstation’s connectivity to the domain and prevent this error from recurring. To avoid this issue in the future, ensure that workstations are removed from the domain properly and that the domain controller maintains a consistent record of computer accounts.