Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Chicagotech MVP | About Us | Contact Us|

Computer Account - Resolution with Screenshots

"The computer account already exists"
"The system cannot log you on now because the domain "name" is not available."
The system cannot log you on to this domain because the system's computer account in its primary domain is missing or the password on that account is incorrect.
The following error occurred attempting to rename the computer to hostname
 

"The computer account already exists"

Symptoms: When joining w2k/xp into a domain, you may receive "The computer account already exists". You may be able to ping the computer account, for example ABC, but ping -a ip address (the same ip of ABC) shows different computer name like XYZ.

Resolution: Go to the DNS ad WINS to find and delete the ABC account and wait for while to re-join the domain.

The system cannot log you on to this domain because the system's computer account in its primary domain is missing or the password on that account is incorrect.

Causes: 1. incorrect password.
2. This behavior may occur if the password for the computer account and the local security authority (LSA) secret are not synchronized.
3. Computer names conflict.

For consultants, refer to the case 082104RL

This account is the same as the one logged on to the system and that this account was tried before to logon
There is no domain controller available to validate this account.
There are currently no logon
servers available to service the logon request.
Event ID 5719

Symptoms: 1. In client, you may receive Event ID 5719: "No Windows NT or Windows 2000 Domain Controller is available for domain Domain. The following error occurred: There are currently no logon servers available to service the logon request."
2. In DC, you may receive Event ID 5719: "No Windows NT or Windows 2000 Domain Controller is available for domain chicagotech.net. The following error occurred: There are currently no logon servers available to service the logon request. 
3. You logon domain user in a domain network, the mapping logon script displays this message: "There is no domain controller available to validate this account."
4. You use a office laptop to connect the office VPN, when you map a network drive using this command line: net use \\chicagotech\shared /u:chicagotech.net/blin, you may receive this message: "This account is the same as the one logged on to the system and that this account was tried before to logon. There is no domain controller available to validate this account"

Causes: 1.The DC is down.
2. Can't access the DC.
3. The DNS issue.
4. Run out of buffer space in the NetBT datagram buffer.

For consultants, refer to the case 112904RL

 

 

  This web is provided "AS IS" with no warranties.
Copyright 2002-2017 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.