This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 43%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hi,
Recently, we found the domain secure channel on Windows Server 2019 broken in our AD. After restart the server, the connection can be resume, but it broken again in a few hour
We tried to reset the secure channel by using Powershell (Test-computersecurechannel -repair), reset the computer account password, and also disjoin and rejoin the server from domain. Both of these method can resume the connection, but the connection will broken again.
This problem only happened on the Windows Server 2019, others OS version like 2012, 2016 don't have this issue.
Any idea?
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Hi,
Any errors in the event log when the issue occurs?
It don't have related errors in event log on both Windows Server 2019 and DC.
We also check the replication and use DCdiag to check all DC, and the result is fine.
Hi,
Please provide details of the error message or symptoms (screen shot) that indicate the secure channel is broken? If the message is during logon then there should be an error in the event logs.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 94%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGK%3C/text%3E%3C/svg%3E)
Did you resolve this issue? We are seeing something very similar. We have 2019 and 2022 DCs. The 2022's are all fine. About half our 2019s are doing this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 89%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJK%3C/text%3E%3C/svg%3E)
Could you please tell how it shows, does it have a specific event id which appears in logs when problem happens, thanks in advance.
Error code 3210 is recorded on systems. Test-computersecurechannel comes back false on any machine authenticating against an effected DC. Trusts to other domains are broken.
No, I didn't solve the issue yet and don't have any idea. It still occurs on Windows 2019 server only.
Hi Chong and Greg,
From A quick net helpmsg....
net helpmsg 3210
This computer could not authenticate with ***, a Windows domain controller
for domain ***, and therefore this computer might deny logon requests.
This inability to authenticate might be caused by another computer on the
same network using the same name or the password for this computer account
is not recognized. If this message appears again, contact your system
administrator.
Assuming you have correctly ruled out the items in the above text then I woud suggest....
Provide some more details of your environment.
e.g. How many Domain Controllers do you have? What OS are they running? have you verified replication is in synch between all DCs? Any unusual networking configuration (NAT/FW/etc.). have you checked all warning and error events (DNS/RPC/Kerberos/Security/LDAP/etc.)? Are your DCs or affected servers Physical or VM? What Virtualisation are you using? Anything which may be different or handled differently by the OS? Do you have any other 2019 servers which are NOT affected? Have you tried another 2019 server?
Anything else which may be specific you your environment or the affected machine(s)
Regards,
Geoff