ERROR_NO_TRUST_SAM_ACCOUNT - 1787 (0x6FB)

The security database on the server does not have a computer account for this workstation trust relationship.

Updated: Feb 21, 2026

Technical Background

The ERROR_NO_TRUST_SAM_ACCOUNT error code, with the numeric value of 1787 and the hexadecimal representation of 0x6FB, indicates a specific issue related to trust relationships in Windows environments. This error is associated with the Security Accounts Manager (SAM) database on a server that does not have an account for the workstation attempting to establish a trust relationship.

Error Details

This error typically occurs when a client machine attempts to authenticate or establish a trust relationship with a domain controller, but the SAM database on the domain controller lacks the necessary computer account. This can lead to authentication failures and other related issues in networked environments where trust relationships are essential for secure communication.

Common Causes

  • Incorrect Trust Relationship Configuration: The client machine may not have established a proper trust relationship with the domain controller, or the trust relationship might be misconfigured.
  • Missing Computer Account: The SAM database on the domain controller does not contain an account corresponding to the workstation attempting to establish the trust relationship.
  • Security Database Corruption: The SAM database might be corrupted, leading to missing or invalid accounts.

Real-World Context

In a Windows domain environment, trust relationships are crucial for ensuring secure communication between different domains. When a client machine attempts to authenticate with a domain controller, it relies on the presence of a corresponding computer account in the SAM database. If this account is missing, the authentication process fails, resulting in the ERROR_NO_TRUST_SAM_ACCOUNT error.

Is This Error Critical?

The criticality of this error depends on the specific context and the importance of the trust relationship in question. In environments where multiple domains or workstations rely on a particular trust relationship for secure communication, this error can be highly disruptive.

How to Diagnose

To diagnose this issue, follow these steps:

  1. Review Trust Relationship Configuration: Ensure that the client machine and the domain controller have established proper trust relationships.
  2. Verify SAM Database Integrity: Check the integrity of the SAM database on the domain controller for any missing or corrupted accounts.
  3. Confirm Computer Account Existence: Verify that the computer account corresponding to the workstation exists in the SAM database.

How to Resolve

To resolve this issue, consider the following steps:

  1. Reconfigure Trust Relationship: Ensure that the trust relationship between the client machine and the domain controller is correctly configured.
  2. Restore or Rebuild SAM Database: If the SAM database is corrupted, it may need to be restored from a backup or rebuilt using appropriate tools provided by Microsoft.
  3. Add Missing Computer Account: If the computer account is missing, add it to the SAM database on the domain controller.

Developer Notes

Developers should ensure that their applications handle authentication and trust relationships appropriately, especially in environments where multiple domains are involved. Proper error handling and logging can help in diagnosing and resolving such issues more effectively.

Related Errors

FAQ

Q: What causes the ERROR_NO_TRUST_SAM_ACCOUNT error?

A: This error typically occurs when the SAM database on the domain controller does not have an account corresponding to the workstation attempting to establish a trust relationship.

Q: How can I prevent this error from occurring?

A: Ensure that proper trust relationships are configured and maintained. Regularly verify the integrity of the SAM database and ensure all necessary accounts are present.

Summary

The ERROR_NO_TRUST_SAM_ACCOUNT error indicates a missing or corrupted computer account in the SAM database, preventing successful authentication and trust relationship establishment between workstations and domain controllers. Diagnosing and resolving this issue involves verifying trust relationships, ensuring SAM database integrity, and managing computer accounts appropriately.