Resolve Windows domain trust relationship error preventing user login

draft · os-and-system domain-joinwindows-login

Generated by docuprocessor (prompt article/v3) · 2026-04-22 13:50

Source thread

thread_id: spaces/AAAA05BdS6s/threads/Psk9tfBPGAk · 14 msgs · first 2024-12-09 · participants: Tech ATech BTech C

Tech A 2024-12-09 15:00

for pds catskill, we have having this error when trying to switch users on the pc, tried unjoining from domain and then join back, same, tried changing the pc name to test (from cart01 to cart1) unjoined domain again, rebooted. joined again with the new name, but same message, any ideas?

image/png image.png

**Windows Login Screen Error** The screen displays a Windows login prompt for **"Other user"** with the error message: *"The security database on the server does not have a computer account for this workstation trust relationship."* An **OK** button is present to dismiss the dialog. No error codes, model numbers, or indicator lights are visible.

Tech B 2024-12-09 15:09

in AD Administrative center look for deleted objects> right click> restore to folder with domain computers > check if that computer is disabled and try to activate/enable it

Tech C 2024-12-09 15:14

is the PC pointed to the correct DNS?

Tech C 2024-12-09 15:14

and what are those DNS servers?

Tech A 2024-12-09 15:40

sorry, I was checking with Albert, but currently primary dns is 172.17.200.11 secondary 172.17.185.25 which is what other pcs are using as well

Tech C 2024-12-09 15:41

is it still an issue or were you able to resolve it?

Tech A 2024-12-09 15:42

not solved yet, as a workaround since they need the pc to work we created a local user that matches the domain one so they can use dentrix and everything, we are still unable to login through any domain user on this pc

Tech C 2024-12-09 15:43

is it connected to the correct WiFi?

Tech A 2024-12-09 15:49

SSID for the one they are on is HQRC Catskill, its able to reach everything on the network, so I guess is the right one?

Tech C 2024-12-09 15:53

is the PC available now to be worked on?

Tech A 2024-12-09 15:55

I don't think so since they were pushing us, let me ask a time where the computer is free, I'll let you know in a few mins

Tech A 2024-12-09 22:07

so this works fine now, I called them to get a chance to use the pc and check, and suddenly is working fine, I can login again to the domain user on the pc. so no idea, but it works now 🙂

Tech C 2024-12-09 22:12

(no text)

Tech B 2024-12-10 10:37

(no text)

---
title: "Resolve Windows domain trust relationship error preventing user login"
category: os-and-system
tags: ["domain-join", "windows-login"]
source_thread_id: "spaces/AAAA05BdS6s/threads/Psk9tfBPGAk"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T13:50:43"
participants: ["Tech A", "Tech B", "Tech C"]
---

# Resolve Windows domain trust relationship error preventing user login

## Problem

A Windows workstation at a PDS office displayed the error "The security database on the server does not have a computer account for this workstation trust relationship" when attempting to switch users or log in with domain credentials. The PC (originally named cart01) was unable to authenticate any domain users despite being connected to the correct network and having proper DNS settings. Standard remediation steps including unjoining and rejoining the domain, and changing the computer name to cart1, did not resolve the issue initially.

## Resolution

The issue resolved itself spontaneously after several hours without additional intervention. However, for similar cases, attempt these troubleshooting steps:

1. Verify DNS configuration matches other working PCs on the network
2. Confirm the workstation is connected to the correct network/SSID
3. Check Active Directory Administrative Center for deleted objects:
   - Right-click on deleted objects
   - Select "restore to folder with domain computers"
   - Verify the computer account is not disabled and enable if necessary
4. As a temporary workaround, create a local user account matching the domain user to maintain system functionality while troubleshooting
5. If the above steps don't work immediately, allow time for domain replication and retry after several hours

The root cause in this case was not definitively identified, but the issue resolved without further action.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/Psk9tfBPGAk`
- Attachments: - ![image.png](../attachments/Psk9tfBPGAk.Psk9tfBPGAk/image.png) — **Windows Login Screen Error**

Generated article

draft