How do I fix SecureChannel connection not active?

Garrick Whetstine 20 Reputation points
2026-11-20T21:25:55.0533333+00:00

I'm trying to fix an issue with a client's server. They're running a Domain Controller on a Dell PowerEdge with Windows Server 2019. The server was renamed in the past. About a year ago, the server was restored from a backup. Only 1 has an established Computer Secure Channel connection. They are using a local QuickBooks server "QB data server" to host their data file, and we were able to get that working properly. The issue now is: SecureChannel connection is not active. My team used an AI chatbot to help with troubleshooting. Here are the summaries:

Windows Active Directory Secure Channel Troubleshooting Report

<badge color="warning">Status: Investigation in Progress</badge>

1. Problem Identified

An issue was identified while attempting to verify the secure channel between a Windows workstation and its Active Directory domain.

The following command was executed from an elevated PowerShell session:

nltest /sc_verify:<DOMAIN_NAME>

The command returned:

Flags: 40000080 Authentication Service: Netlogon

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

Initial interpretation:

Windows attempted to verify the workstation's secure channel with Active Directory but received an Access Denied (Error 5) response.

The command executed successfully, but the actual trust verification failed.

2. Network Configuration Reviewed

The workstation's network configuration was reviewed using:

ipconfig /all

The following general configuration was identified:

Configuration Finding
Computer name Redacted
Primary DNS suffix Redacted
IPv4 configuration Private network address
Subnet mask /24 network
Default gateway Redacted
DNS server Internal DNS server
DHCP Disabled on active wireless adapter
Network connection Wireless
NetBIOS over TCP/IP Enabled

Additional network adapters were present but disconnected.

Initial assessment:

The workstation appears to be configured to use an internal DNS server rather than a public DNS service.

However, DNS resolution and domain controller connectivity have not yet been verified.

3. Troubleshooting Steps Identified

Three primary areas of investigation were established.

A. Domain Controller Discovery and DNS

Commands:

nslookup <DOMAIN_NAME>
nslookup -type=SRV _ldap._tcp.dc._msdcs.<DOMAIN_NAME>

Purpose:

Verify domain DNS resolution.

Identify domain controllers registered in DNS.

Confirm that Active Directory SRV records are available.

B. Domain Controller Connectivity

The following connectivity tests were recommended:

Test-NetConnection <DC_IP_ADDRESS> -Port 88
Test-NetConnection <DC_IP_ADDRESS> -Port 389
Test-NetConnection <DC_IP_ADDRESS> -Port 445
Test-NetConnection <DC_IP_ADDRESS> -Port 135

Purpose:

Port Service
88 Kerberos
389 LDAP
445 SMB
135 RPC Endpoint Mapper

These tests help determine whether the workstation can communicate with essential Active Directory services.

Note: Successful TCP connectivity tests do not independently prove that all domain authentication services are functioning.

C. Secure Channel Verification

Command:

Test-ComputerSecureChannel -Verbose

Purpose:

Determine whether the workstation's secure channel is functioning.

Obtain additional troubleshooting information.

Identify whether a computer account trust issue may exist.

4. Current Findings

Investigation Item Status
Domain DNS suffix configured Confirmed
Internal DNS server configured Confirmed
Network configuration reviewed Confirmed
Secure channel verification Failed – Access Denied
Domain controller discovery Not tested
DNS SRV record verification Not tested
Domain service connectivity Not tested
Computer account trust Not confirmed

Before attempting any repairs, collect the following information:

Confirm that the configured DNS server is an authorized Active Directory DNS server.

Run the two DNS lookup commands.

Execute:

nltest /dsgetdc:<DOMAIN_NAME> /force

Execute:

Test-ComputerSecureChannel -Verbose

Complete the four domain controller connectivity tests.

6. Changes Made

No corrective changes have been performed.

Specifically:

The computer account password has not been reset.

The secure channel has not been repaired.

The workstation has not been removed from the domain.

No Active Directory account modifications have been performed.

No DNS or network configuration changes have been made.

7. Preliminary Diagnosis

Three possible causes remain under investigation:

1. Domain Controller Communication

The workstation may not be communicating properly with the domain controller due to DNS, network connectivity, firewall, or service availability issues.

2. Computer Account Trust

The workstation's locally stored machine account password may not match the password stored in Active Directory.

3. Authentication or Permissions

The domain controller may be rejecting the authentication request because of an authentication, authorization, or security configuration issue.

Additional diagnostic results are required before determining the root cause.

Proceed in the following order:

Verify DNS resolution.

Identify the domain controller.

Verify network connectivity to domain services.

Test the workstation's secure channel.

Review relevant authentication and Netlogon events.

Perform corrective actions only after identifying the underlying issue.

Conclusion:

The investigation has identified a failed Active Directory secure channel verification returning ERROR_ACCESS_DENIED (0x5).

The workstation's basic network configuration appears reasonable, but domain controller connectivity, authentication, and computer account trust have not yet been fully validated.

The investigation remains open pending additional diagnostic results.

Windows Active Directory Secure Channel Troubleshooting Report

<badge color="warning">Status: Investigation in Progress</badge>

1. Problem Identified

An issue was identified while attempting to verify the secure channel between a Windows workstation and its Active Directory domain.

The following command was executed from an elevated PowerShell session:

nltest /sc_verify:<DOMAIN_NAME>

The command returned:

Flags: 40000080 Authentication Service: Netlogon

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

Initial interpretation:

Windows attempted to verify the workstation's secure channel with Active Directory but received an Access Denied (Error 5) response.

The command executed successfully, but the actual trust verification failed.

2. Network Configuration Reviewed

The workstation's network configuration was reviewed using:

ipconfig /all

The following general configuration was identified:

Configuration Finding
Computer name Redacted
Primary DNS suffix Redacted
IPv4 configuration Private network address
Subnet mask /24 network
Default gateway Redacted
DNS server Internal DNS server
DHCP Disabled on active wireless adapter
Network connection Wireless
NetBIOS over TCP/IP Enabled

Additional network adapters were present but disconnected.

Initial assessment:

The workstation appears to be configured to use an internal DNS server rather than a public DNS service.

However, DNS resolution and domain controller connectivity have not yet been verified.

3. Troubleshooting Steps Identified

Three primary areas of investigation were established.

A. Domain Controller Discovery and DNS

Commands:

nslookup <DOMAIN_NAME>
nslookup -type=SRV _ldap._tcp.dc._msdcs.<DOMAIN_NAME>

Purpose:

Verify domain DNS resolution.

Identify domain controllers registered in DNS.

Confirm that Active Directory SRV records are available.

B. Domain Controller Connectivity

The following connectivity tests were recommended:

Test-NetConnection <DC_IP_ADDRESS> -Port 88
Test-NetConnection <DC_IP_ADDRESS> -Port 389
Test-NetConnection <DC_IP_ADDRESS> -Port 445
Test-NetConnection <DC_IP_ADDRESS> -Port 135

Purpose:

Port Service
88 Kerberos
389 LDAP
445 SMB
135 RPC Endpoint Mapper

These tests help determine whether the workstation can communicate with essential Active Directory services.

Note: Successful TCP connectivity tests do not independently prove that all domain authentication services are functioning.

C. Secure Channel Verification

Command:

Test-ComputerSecureChannel -Verbose

Purpose:

Determine whether the workstation's secure channel is functioning.

Obtain additional troubleshooting information.

Identify whether a computer account trust issue may exist.

4. Current Findings

Investigation Item Status
Domain DNS suffix configured Confirmed
Internal DNS server configured Confirmed
Network configuration reviewed Confirmed
Secure channel verification Failed – Access Denied
Domain controller discovery Not tested
DNS SRV record verification Not tested
Domain service connectivity Not tested
Computer account trust Not confirmed

Before attempting any repairs, collect the following information:

Confirm that the configured DNS server is an authorized Active Directory DNS server.

Run the two DNS lookup commands.

Execute:

nltest /dsgetdc:<DOMAIN_NAME> /force

Execute:

Test-ComputerSecureChannel -Verbose

Complete the four domain controller connectivity tests.

6. Changes Made

No corrective changes have been performed.

Specifically:

The computer account password has not been reset.

The secure channel has not been repaired.

The workstation has not been removed from the domain.

No Active Directory account modifications have been performed.

No DNS or network configuration changes have been made.

7. Preliminary Diagnosis

Three possible causes remain under investigation:

1. Domain Controller Communication

The workstation may not be communicating properly with the domain controller due to DNS, network connectivity, firewall, or service availability issues.

2. Computer Account Trust

The workstation's locally stored machine account password may not match the password stored in Active Directory.

3. Authentication or Permissions

The domain controller may be rejecting the authentication request because of an authentication, authorization, or security configuration issue.

Additional diagnostic results are required before determining the root cause.

Proceed in the following order:

Verify DNS resolution.

Identify the domain controller.

Verify network connectivity to domain services.

Test the workstation's secure channel.

Review relevant authentication and Netlogon events.

Perform corrective actions only after identifying the underlying issue.

Conclusion:

The investigation has identified a failed Active Directory secure channel verification returning ERROR_ACCESS_DENIED (0x5).

The workstation's basic network configuration appears reasonable, but domain controller connectivity, authentication, and computer account trust have not yet been fully validated.

The investigation remains open pending additional diagnostic results.

Active Directory Troubleshooting Summary

1. Customer environment

Component

|| | -------- | Configuration

|| || Domain

|| || Customer domain

|| || Domain Controller

|| || Primary DC

|| || Operating System

|| || Windows Server 2019 Essentials

|| || Server IP

|| || Private internal IP

|| || Gateway

|| || Internal network gateway

|| || Internal DNS

|| || Domain controller

|| || Workstations

|| || 4 Windows 11 Pro PCs

|| || Previous server name

|| || Original server hostname

|| || Current server name

|| || Renamed server hostname

2. Original problem

The domain controller was accidentally renamed.

Following the rename and reboot, workstations began identifying their network connections as Public instead of DomainAuthenticated.

This suggested that workstations were having trouble authenticating with Active Directory.

3. Domain controller diagnostics

We performed several diagnostic checks to establish whether Active Directory was still functioning.

Initial checks passed

We confirmed:

The server hostname was updated.

The server remained joined to its domain.

DomainRole reported 5 (Domain Controller).

NTDS was running.

DNS was running.

Netlogon was running.

KDC was running.

DFSR was running.

Server IP and DNS configuration were correct.

Domain controller discovery worked.

DNS A records were registered.

SPN registrations were present.

We successfully executed:

nltest /dsgetdc:<domain-name> /force

The server correctly identified itself as the domain controller.

We also ran:

netdom computername <server-fqdn> /verify

DNS registrations and SPNs were verified.

Conclusion: The domain controller appears operational, although a comprehensive Active Directory health assessment has not been completed.

4. Workstation troubleshooting

We investigated three of the four workstations.

Workstation 1

Successfully repaired

Initially, this workstation had a broken domain secure channel.

We confirmed that it could:

Communicate with the domain controller.

Resolve the domain controller.

Connect over LDAP.

Remain joined to the domain.

However:

Test-ComputerSecureChannel -Verbose

Returned:

False

We repaired it using Microsoft's machine-account password reset method.

First:

$cred = Get-Credential

We supplied authorized domain administrator credentials.

Then:

Reset-ComputerMachinePassword -Server "<domain-controller-fqdn>" -Credential $cred -ErrorAction Stop -Verbose

Afterward:

Test-ComputerSecureChannel -Verbose

Returned:

True

We also confirmed:

Get-NetConnectionProfile

The network category changed to:

NetworkCategory : DomainAuthenticated

Conclusion: The workstation's domain trust was successfully restored without removing it from the domain.

Workstation 2

Still unresolved

We confirmed:

Correct internal DNS configuration.

Successful domain controller discovery.

Computer remained domain-joined.

PartOfDomain returned True.

However:

Test-ComputerSecureChannel -Verbose

Continued returning:

False

We attempted the same machine-account password reset used on the previously repaired workstation:

Reset-ComputerMachinePassword -Server "<domain-controller-fqdn>" -Credential $cred -ErrorAction Stop -Verbose

Although the command completed without displaying an error, the secure channel remained broken.

We subsequently ran:

nltest /sc_query:<domain-name>

It returned:

Trusted DC Connection Status Status = 5
0x5 ERROR_ACCESS_DENIED

Conclusion: This workstation has a persistent domain trust/authentication problem that the standard machine-password reset did not resolve.

Workstation 3

Needs verification

This workstation was one of the first investigated.

We confirmed:

Successful communication with the domain controller.

Successful LDAP connectivity.

Successful domain controller discovery.

Broken secure channel.

We also identified these Netlogon events:

Event ID

|| | -------- | Description

|| || 3210

|| || Workstation authentication failure

|| || 5719

|| || Unable to establish secure session with domain controller

We have not yet confirmed whether this workstation's secure channel has been repaired.

Workstation 4

Not investigated

No troubleshooting has been completed on this workstation yet.

5. DNS configuration investigation

We discovered that some network adapters had additional DNS servers configured, including:

The internal domain controller.

The network gateway.

A public DNS provider.

We identified this as a potential configuration problem.

However, we subsequently verified that the unresolved workstation's active Wi-Fi adapter uses only the internal domain controller for DNS.

Therefore, we have not established DNS configuration as the cause of its failure.

We should still investigate DHCP configuration and DNS settings across the remaining workstations.

6. Current status

Device

|| | -------- | Status

|| || Domain Controller

|| || Initial checks passed

|| || Workstation 1

|| || Repaired

|| || Workstation 2

|| || Unresolved

|| || Workstation 3

|| || Needs verification

|| || Workstation 4

|| || Not investigated

7. Where troubleshooting left off

The last command requested on the unresolved workstation was:

nltest /sc_verify:<domain-name>

We need its complete output, especially the error code.

Afterward, we planned to investigate the workstation's Active Directory computer account.

On the affected workstation:

hostname
nltest /dsgetdc:<domain-name> /force

On the domain controller, using an elevated PowerShell session with the Active Directory module:

Get-ADComputer -Identity "<computer-name>" -Properties Enabled,PasswordLastSet,DNSHostName,ServicePrincipalName |
Format-List Name,Enabled,PasswordLastSet,DNSHostName,ServicePrincipalName

We also want to inspect the domain controller's:

System event log.

Directory Service event log.

Netlogon-related events.

8. Actions deliberately avoided

We have not:

Renamed the domain controller again.

Deleted workstation computer accounts.

Removed workstations from the domain.

Rebuilt Active Directory.

Modified existing user profiles.

Made unnecessary changes to the domain controller.

These precautions are important because the domain controller is still operational, and we have already successfully repaired one workstation.

9. Overall assessment

Based on the troubleshooting completed:

The domain controller appears to be functioning normally based on initial checks.

The original server rename may have contributed to the authentication problems, but this has not been established.

Workstation machine-account authentication is a confirmed problem.

Resetting the machine-account password successfully repaired one workstation.

A second workstation presents a more complicated problem because the same repair procedure did not restore its secure channel.

Additional investigation is necessary to determine whether the unresolved workstation has a computer-account issue, authentication issue, or broader domain-side problem.

Recommended next step: Continue troubleshooting the unresolved workstation before making additional changes to Active Directory. Determine why the machine-account password reset worked on one workstation but not the other.

Active Directory Troubleshooting Summary

1. Customer environment

|| | -------- | Component

|| | -------- | Configuration

|| || Domain

|| || Customer domain

|| || Domain Controller

|| || Primary DC

|| || Operating System

|| || Windows Server 2019 Essentials

|| || Server IP

|| || Private internal IP

|| || Gateway

|| || Internal network gateway

|| || Internal DNS

|| || Domain controller

|| || Workstations

|| || 4 Windows 11 Pro PCs

|| || Previous server name

|| || Original server hostname

|| || Current server name

|| || Renamed server hostname

2. Original problem

The domain controller was accidentally renamed.

Following the rename and reboot, workstations began identifying their network connections as Public instead of DomainAuthenticated.

This suggested that workstations were having trouble authenticating with Active Directory.

3. Domain controller diagnostics

We performed several diagnostic checks to establish whether Active Directory was still functioning.

Initial checks passed

We confirmed:

The server hostname was updated.

The server remained joined to its domain.

DomainRole reported 5 (Domain Controller).

NTDS was running.

DNS was running.

Netlogon was running.

KDC was running.

DFSR was running.

Server IP and DNS configuration were correct.

Domain controller discovery worked.

DNS A records were registered.

SPN registrations were present.

We successfully executed:

nltest /dsgetdc:<domain-name> /force

The server correctly identified itself as the domain controller.

We also ran:

netdom computername <server-fqdn> /verify

DNS registrations and SPNs were verified.

Conclusion: The domain controller appears operational, although a comprehensive Active Directory health assessment has not been completed.

4. Workstation troubleshooting

We investigated three of the four workstations.

Workstation 1

Successfully repaired

Initially, this workstation had a broken domain secure channel.

We confirmed that it could:

Communicate with the domain controller.

Resolve the domain controller.

Connect over LDAP.

Remain joined to the domain.

However:

Test-ComputerSecureChannel -Verbose

Returned:

False

We repaired it using Microsoft's machine-account password reset method.

First:

$cred = Get-Credential

We supplied authorized domain administrator credentials.

Then:

Reset-ComputerMachinePassword -Server "<domain-controller-fqdn>" -Credential $cred -ErrorAction Stop -Verbose

Afterward:

Test-ComputerSecureChannel -Verbose

Returned:

True

We also confirmed:

Get-NetConnectionProfile

The network category changed to:

NetworkCategory : DomainAuthenticated

Conclusion: The workstation's domain trust was successfully restored without removing it from the domain.

Workstation 2

Still unresolved

We confirmed:

Correct internal DNS configuration.

Successful domain controller discovery.

Computer remained domain-joined.

PartOfDomain returned True.

However:

Test-ComputerSecureChannel -Verbose

Continued returning:

False

We attempted the same machine-account password reset used on the previously repaired workstation:

Reset-ComputerMachinePassword -Server "<domain-controller-fqdn>" -Credential $cred -ErrorAction Stop -Verbose

Although the command completed without displaying an error, the secure channel remained broken.

We subsequently ran:

nltest /sc_query:<domain-name>

It returned:

Trusted DC Connection Status Status = 5
0x5 ERROR_ACCESS_DENIED

Conclusion: This workstation has a persistent domain trust/authentication problem that the standard machine-password reset did not resolve.

Workstation 3

Needs verification

This workstation was one of the first investigated.

We confirmed:

Successful communication with the domain controller.

Successful LDAP connectivity.

Successful domain controller discovery.

Broken secure channel.

We also identified these Netlogon events:

|| | -------- | Event ID

|| | -------- | Description

|| || 3210

|| || Workstation authentication failure

|| || 5719

|| || Unable to establish secure session with domain controller

We have not yet confirmed whether this workstation's secure channel has been repaired.

Workstation 4

Not investigated

No troubleshooting has been completed on this workstation yet.

5. DNS configuration investigation

We discovered that some network adapters had additional DNS servers configured, including:

The internal domain controller.

The network gateway.

A public DNS provider.

We identified this as a potential configuration problem.

However, we subsequently verified that the unresolved workstation's active Wi-Fi adapter uses only the internal domain controller for DNS.

Therefore, we have not established DNS configuration as the cause of its failure.

We should still investigate DHCP configuration and DNS settings across the remaining workstations.

6. Current status

|| | -------- | Device

|| | -------- | Status

|| || Domain Controller

|| || Initial checks passed

|| || Workstation 1

|| || Repaired

|| || Workstation 2

|| || Unresolved

|| || Workstation 3

|| || Needs verification

|| || Workstation 4

|| || Not investigated

7. Where troubleshooting left off

The last command requested on the unresolved workstation was:

nltest /sc_verify:<domain-name>

We need its complete output, especially the error code.

Afterward, we planned to investigate the workstation's Active Directory computer account.

On the affected workstation:

hostname
nltest /dsgetdc:<domain-name> /force

On the domain controller, using an elevated PowerShell session with the Active Directory module:

Get-ADComputer -Identity "<computer-name>" -Properties Enabled,PasswordLastSet,DNSHostName,ServicePrincipalName |
Format-List Name,Enabled,PasswordLastSet,DNSHostName,ServicePrincipalName

We also want to inspect the domain controller's:

System event log.

Directory Service event log.

Netlogon-related events.

8. Actions deliberately avoided

We have not:

Renamed the domain controller again.

Deleted workstation computer accounts.

Removed workstations from the domain.

Rebuilt Active Directory.

Modified existing user profiles.

Made unnecessary changes to the domain controller.

These precautions are important because the domain controller is still operational, and we have already successfully repaired one workstation.

9. Overall assessment

Based on the troubleshooting completed:

The domain controller appears to be functioning normally based on initial checks.

The original server rename may have contributed to the authentication problems, but this has not been established.

Workstation machine-account authentication is a confirmed problem.

Resetting the machine-account password successfully repaired one workstation.

A second workstation presents a more complicated problem because the same repair procedure did not restore its secure channel.

Additional investigation is necessary to determine whether the unresolved workstation has a computer-account issue, authentication issue, or broader domain-side problem.

Recommended next step: Continue troubleshooting the unresolved workstation before making additional changes to Active Directory. Determine why the machine-account password reset worked on one workstation but not the other.

  • After the server rebooted, it dropped its domain network profile, and the domain secure channel broke for several machines.
  • QuickBooks file access was restored by remapping the QBW file on each workstation and placing it in multi-user mode.
  • AnyDesk access was fixed by adding a Bitdefender firewall rule.
  • Machine-password resets restored the secure channel only on WK-04 workstation.
  • A DNS delegation error was identified: the _msdcs NS record for Domain points to an outdated server name.

Open issues:

  • The domain secure channel is still inactive on WK-01, WK-02, AND WK-03 workstations.
  • The _msdcs parent-zone NS delegation points to sw-server.domain.com instead of SUL-SWO-SRV-01.
  • QuickBooks still needs the QBW remap and multi-user setup on the remaining workstations.
  • Renaming the server and workstations to the planned naming scheme has not been completed because of an "access is denied" error.
  • The server runs end-of-life Windows Server 2019 Essentials with failed Windows updates. Bitdefender and NinjaBackup status is unverified.

Next steps:

  1. Correct the DNS NS record for Domain.
  2. Verify the fix with dcdiag /test:dns /v.
  3. Rerun Test-ComputerSecureChannel on (WK-01) and (WK-02) workstations.
  4. Remap QuickBooks in multi-user mode on the remaining workstations.
    • After the server rebooted, it dropped its domain network profile, and the domain secure channel broke for several machines.
  • QuickBooks file access was restored by remapping the QBW file on each workstation and placing it in multi-user mode.
  • AnyDesk access was fixed by adding a Bitdefender firewall rule.
    • Machine-password resets restored the secure channel only on WK-04 workstation.
    • A DNS delegation error was identified: the _msdcs NS record for Domain points to an outdated server name.
    Open issues:
    • The domain secure channel is still inactive on WK-01, WK-02, AND WK-03 workstations.
    • The _msdcs parent-zone NS delegation points to Domain instead of SUL-SWO-SRV-01.
    • QuickBooks still needs the QBW remap and multi-user setup on the remaining workstations.
    • Renaming the server and workstations to the planned naming scheme has not been completed because of an "access is denied" error.
    • The server runs end-of-life Windows Server 2019 Essentials with failed Windows updates. Bitdefender and NinjaBackup status is unverified.
    Next steps:
    1. Correct the DNS NS record for Domain.
    2. Verify the fix with dcdiag /test:dns /v.
    3. Rerun Test-ComputerSecureChannel on (WK-01) and (WK-02) workstations.
    4. Remap QuickBooks in multi-user mode on the remaining workstations.
Windows for business | Windows Server | Directory services | Active Directory
0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.