Solution for the error-”This computer could not authenticate with Domain Controller”
Sometimes in an Active directory environment administrators may find problems that the Domain users/administrators are not able to login to a member server or a client where they can able to login as local admin. Upon“This computer could not authenticate with DomainController’ a Windows domain controller for domain 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.”
Possible causes
- The problematic system was powered off more than the days the password expiry days mentioned in the domain group policy.
- The secure channel between DC and problematic system is broken.
- Make the
server back to Workgroup and rejoin the domain. - Reset the computer password, to do this follow the steps below
2. Issue the command “klist purge” to clear the Kerberos ticket cache on this server. If your server doesn’t have klist command, you could
http://www.microsoft.com/en-us/download/details.aspx?id=17657
3. Type the command “netdom resetpwd /s:x.x.x.x /ud:domain\User /pd:*”
In this command, please use the PDC’s IP address replace the x.x.x.x; Use your domain administrator replace the domain\user, like this “your domain\administrator”
4. After that, the system will ask your domain administrator’s password, please type it on CMD;
5. After the execution of all commands you should restart the machine and try to login with the domain admin user.
If this is not working Make the server back to Workgroup and rejoin domain to do it without losing its SID follow these two steps.
- In AD right click the computer and select Reset Account. Then re-join without un-joining the computer to the domain. Reboot required.
- In an elevated
command prompt type: nltest /Server: ServerName /SC_Reset:Domain\DomainController No rejoin. No reboot.
0 comments:
Post a Comment