[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

event id 5723 on win 2003 server

I'm getting a lot of 5723 events on a DC computer. Here is the event log text:

Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5723
Date:            8/8/2010
Time:            1:46:45 PM
User:            N\A
Computer:      xxxxxxx-xxx
Description:


The session setup from computer 'VM-WIN2K3APP' failed because the security database does not contain a trust account 'VM-WIN2K3APP$' referenced by the specified computer.  

USER ACTION  
If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. Otherwise, the following steps may be taken to resolve this problem:  

If 'VM-WIN2K3APP$' is a legitimate machine account for the computer 'VM-WIN2K3APP', then 'VM-WIN2K3APP' should be rejoined to the domain.  

If 'VM-WIN2K3APP$' is a legitimate interdomain trust account, then the trust should be recreated.  

Otherwise, assuming that 'VM-WIN2K3APP$' is not a legitimate account, the following action should be taken on 'VM-WIN2K3APP':  

If 'VM-WIN2K3APP' is a Domain Controller, then the trust associated with 'VM-WIN2K3APP$' should be deleted.  

If 'VM-WIN2K3APP' is not a Domain Controller, it should be disjoined from the domain.

Any ideas on how to deal with this?

0
johnf23
Asked:
johnf23
1 Solution
 
Pete LongConsultantCommented:
the clues in the error m8? if its NOT a domain controller leave the domain then rejoin it - if it is a domain controller then you will have to jump though a few hoops
0
 
Krzysztof PytkoActive Directory EngineerCommented:
I can see that it is your application server. So, the problem is with server password (authentication with domain). Find its account in ADUC, click right mouse button and choose "Reset account" then disjoint it from the domain. Reboot server and join it to the domain once again. It will preserve its membership and properties.
0
 
Lukasz ChmielewskiCommented:
Disable the machine firewall and rejoin the domain.
0
 
johnf23Author Commented:
OK I will test it
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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