Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 836
  • Last Modified:

Event ID: 5722

Get following error on dc.
Also get error when I try to remote in to computer (AP24-PC) using my log me in pro.

error (login): the trust relationship between this workstation and the primary domain failed. (1789)

Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5722
Date:            11/21/2013
Time:            12:59:21 PM
User:            N/A
Computer:      SERVER
Description:
The session setup from the computer AP24-PC failed to authenticate. The name(s) of the account(s) referenced in the security database is AP24-PC$.  The following error occurred:
Access is denied.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 c0               "..À
0
jyoung127
Asked:
jyoung127
2 Solutions
 
Zac HarrisCommented:
There are many different ways to fix this issue. Here are two I use:

Quick n Dirty:
Unjoin the computer from the domain then rejoin the computer to the domain.

Powershell:
Reset-ComputerMachinePassword [-Credential <PSCredential>] [-Server <String>]

HTH
0
 
MaheshArchitectCommented:
In a Microsoft Windows domain, starting with Windows 2000, a discrete communication channel helps provide a more secure communication path between the domain controller and the member servers or workstations. This channel is known as a secure channel. When you join a computer to a domain, a computer account is created, and a password is shared between the computer and the domain controller. By default, this password is changed every 30 days. The secure channel's password is stored together with the computer account on the primary domain controller (PDC). The password is replicated to all replica domain controllers.
The error basically occurs due to duplicate/conflicting object in the AD as well as DNS causing machine is not able to refresh its password end up in broken secure channel.
Means actual computer password and one stored on domain controller do not match and simply domain controller rejects the autheticatin request.
http://support.microsoft.com/kb/810977

You can do below as simplest method
Reset affected computer account on domain controller
Disjoin affected computer to workgroup and reboot
join workgroup computer to domain again and reboot
Post reboot logon with domain account and check if below commands are working
Go to run and enter %logonserver%    - this should resolve to local \ authenticating DC
Go to cmd and enter nltest /dsgetdc:domain.com
nslookup should resolve to local \ autheticating DC

Mahesh
0
 
jyoung127Author Commented:
Thank you for your response I figured I had to dis oin it from domain I was looking to see if there was an easier way but I think that sounds to me like that will be the easiest way.

Thank you all
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now