Netlogon Error
A virtual server machine (2003 server) moved from one system to other system. After moving the virtual machine, in DC event viewer we are getting NETLOGON error. Event Type: ErrorEvent Source: NETLOGONEvent Category: NoneEvent ID: 5722Date: DateTime: TimeUser: N/AComputer: ComputerNameDescription: The session setup from the computer ComputerName failed to authenticate. The name of the account referenced in the security database is AccountName$.The following error occurred:Access is denied. Domain user accounts are unable to login into that server. It is not accepting local administrator password or we lost the password not sure. Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. Anyone pls provide me the solution...Sree
September 2nd, 2008 1:46pm

Hi!I googled microsoft article about"Resetting computer accounts in Windows".http://support.microsoft.com/kb/216393Hope this helps.Henry Eklf :: Just one random IT-guy more.
Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2008 1:08pm

Hi Sree, As your description, you have encountered the logon failure issue on one member server after you move the virtual system from one host to another. I suspect this may be caused by the broken of the secure channel between the member server and the domain controller. Troubleshoot steps: 1. Please first check on the network connection properties of the problematic server to see if the DNS has been pointed to the correct DNS server in the domain. 2. Please also the DNS suffix on the member server and on the domain to check if the DNS suffix on the member server matches that of the domain. 3. Please disjoin the problematic member server from the domain. 4. Remove the computer account of the computer account of the problematic server in "Active Directory Users and Computers" 5. Rejoin the server to the Windows Server 2003 domain to rebuild the secure channel, and then logon the domain with domain administrator account to check if the issue can be resolved. Hope it helps.David Shen - MSFT
September 3rd, 2008 2:19pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics