I’m troubleshooting what appears to be an Active Directory secure-channel or domain trust issue and would appreciate input from anyone who has dealt with something similar.
Environment
- Domain: Internal Active Directory domain (name omitted)
- Domain Controller: Windows Server 2019 Essentials
- Domain Controllers: One
- DNS: Active Directory-integrated DNS hosted on the domain controller
- Backup software: NinjaOne Backup
- Recovery method: Restored the server from backup using a clone restore
- Affected workstation: Windows domain-joined workstation
The issue appeared in the context of restoring the domain controller from backup. I’m trying to determine whether the restore process, AD metadata, DNS, or computer account passwords could be involved.
Symptoms
On an affected workstation, running:
nltest /sc_verify:<domain-name>
Returns:
Flags: 40000080
Trusted DC Name
Trusted DC Connection Status Status = 5 0x5 ERROR_ACCESS_DENIED
Trust Verification Status = 5 0x5 ERROR_ACCESS_DENIED
The command completed successfully
The command itself completes, but secure-channel verification reports Access Denied.
What I’ve checked so far
1. Workstation DNS configuration
The workstation is configured to use the domain controller for DNS. Its primary DNS suffix matches the Active Directory domain.
2. Domain controller health
Ran DCDIAG against the domain controller.
The following tests passed:
- Connectivity
- Advertising
- DFSREvent
- SysVolCheck
- KccEvent
- KnowsOfRoleHolders
- MachineAccount
- NCSecDesc
- NetLogons
- ObjectsReplicated
- Replications
- RidManager
- Services
- SystemLog
- VerifyReferences
- LocatorCheck
There is only one domain controller in this environment, so there is no second DC to compare against.
3. DNS diagnostics
dcdiag /test:dns /v reports a DNS delegation problem:
Delegated domain name: _msdcs.<domain-name>.
Error:
DNS server: <old-server-name>.
IP: <Unavailable>
[Missing glue A record]
Further investigation revealed:
- The actual
_msdcsDNS zone has an NS record pointing to the current domain controller. - However, the
_msdcsNS record in the parent domain zone still points to an old server hostname. - That old hostname no longer resolves in DNS.
- The current domain controller’s DNS records and AD-integrated zones otherwise appear to be present.
This appears to be a stale DNS delegation left over from an older server name.
4. DNS forwarders
DCDIAG also reported two unreachable DNS forwarders. A public DNS forwarder passed its tests.
Questions for the community
- Could an incorrect
_msdcsdelegation causenltest /sc_verifyto returnERROR_ACCESS_DENIED, or is that error more indicative of a computer account password mismatch? - Could restoring a domain controller using NinjaOne Backup’s clone restore cause an AD database, invocation ID, USN, or computer account password inconsistency?
- Is there anything specific I should verify after restoring a domain controller from a clone-based backup, especially when it is the only DC in the domain?
- Would you recommend correcting the stale
_msdcsdelegation first and then retesting the secure channel, or investigating the workstation’s computer account password first? - Are there particular Event Viewer logs or event IDs I should examine on the DC to identify whether this is an AD authentication, Netlogon, Kerberos, or DNS issue?
- What is the safest way to test the secure channels of all domain-joined workstations without unnecessarily resetting computer accounts or disrupting users?
- Are there any additional PowerShell commands or diagnostic tools you would recommend before attempting to repair the secure channel?
What I’m trying to avoid
I don’t want to start removing/rejoining computers to the domain or resetting computer accounts until I understand whether the underlying issue is DNS, AD, or something related to the server restore.
I’d especially appreciate input from anyone who has recovered a Windows Server 2019 domain controller using NinjaOne Backup or another image/clone-based backup solution.
Thanks!