Ever remember a computer in an edit as domain maintains a computer account with a user name which is
Sam account name and password.
Just like a user account does the computer restore its password in the form of a local security authority.
Or let's say secret and changes it but it's password with a domain approximately every 30 days.
The net logon service uses the credentials to assign into the domain which establishes a secure channel
with a domain controller.
Computer accounts and the relationships between computers and their domain are generally robust.
Nevertheless there are certain scenarios in which a computer can not authenticate with the domain.
When this happens users are unable to sign in and the computer can not access the resources such as
group policy.
Example Say of scenarios where this can happen include the following after reinstalling the operating
system on a workstation liver extension cannot authenticate even though the technician is used the same
computer name used in the previous installation because the new installation generated and you see it.
And because the new computer does not know the original computer account password in the domain it does
not belong to the domain and can not authenticate to the domain.
Another scenario is a computer has not been in use for a for an extended period perhaps because the
user was walking away from the office or the computer was rebuilt to the spare.
During this period an administrator must have researched or deleted the computer recall.
Another scenario is a computer's LSA secret gets out of synchronization with a password that the domain
knows you can think of this as the computer forget and its password.
The computer and the domain do not agree on the correct password.
When this happens the computer can not authenticate and a secure channel cannot be created.
So let's discuss the steps that you should take in these scenarios.
When the security relationship between a computer account and its domain is broken the result is in
numerous potential symptoms sound errors.
The most common signs of computer account problems are messages at sign in indicate that a domain controller
cannot be contacted that the computer recount might be missing that the password on the computer account
is incorrect or that the trust relationships also call to the secure relationship between the computer
and the domain has been lost.
You might encounter error messages or rewound and the event log indicating similar problems or suggesting
that passwords trust secure channels or relationships with a domain or domain controller have failed.
One such error is not log on a wound tidied 32 10 failed to authenticate which appears in the computer
around log when the secure channel fails you must resent it.
Many administrators do this by removing the computer from the domain putting it in a very group and
then rejoining the computer to the domain removing the computer from the domain disables the computer
account in a tedious when you rejoin the computer to the domain it reuses the same computer account
but loses its group memberships do not rename the computer when you rejoin it to the domain you call.
You also can reset the secure channel between a domain member and a domain by using Active Directory
Users and Computers.
Active Directory administrative center the a smart command line tool or not dorm command line tool or
an old task command land tool.
If you reset the account the computer's seat remains the same and the computer maintains its group memberships
to reset the secure a channel by using Active Directory user or some computer or saw Active Directory
administrative center.
Follow this procedure.
Right click the computer and then click reset account.
Click yes to confirm your choice rejoin the computer to the domain and then restart the computer.
Said the secure channel by using diesel smart follows this procedure at a command line at a command
prompt type the following command.
The smart computer in double quotes computer distinguished name Dash.
Reset then rejoin the computer to the domain and then restart the computer.
You can also perform this section with the help of Nat dom.
So to reserve the secure a channel by using net dumb type the following command to the command prompt
where the credentials belong to the local administrators group or the computer type not dumb reset mission
name slash domain and followed by domain name slash user followed by user name and slash for zero followed
by password this command resets the secure channel by attempting to reset the password on both the computer
and the domain so it does not require rejoining or rebooting to reset the secure channel by using an
old test command on the computer that has lost its thrust tab the following command at a command prompt
and all test slash server call on server name slash as C underscore research call on domain backslash
domain controller name you also can use the active directory module for Windows power cell to reset
a computer recall to reset the security channel between the local computer and its domain run the command
on the local computer test computer secure a channel dash repair you can use this command RT Also by
type and invoke command dash computer name followed by the name of the computer that script block and
reset this computer machine password in curly braces.
So lots of choices you could do it to try and run each of these command for your practice and then choose
the preferred method which CO2.