Domain Join Error
An attempt to resolve the DNS name of a DC in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.
An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target Domain.
An operation was attempted on a nonexistent network connection.
You have exceeded the maximum number of computer accounts you are allowed to create in this domain.
Logon failure: The target account name is incorrect.
Logon failure: the user has not been granted the requested logon type at this computer.
Logon failure: unknown user name or bad password.
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
Network name cannot be found.
No mapping between account names and security IDs was done.
No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.
Not enough storage is available to complete this operation.
To resolve this issue, you need to increase the Kerberos token size of the computer you are joining to the domain.
The account specified for this service is different from the account specified for other services running in the same process.
The directory service has exhausted the pool of relative identifiers.
Richard Mueller edited Revision 21. Comment: Removed (en-US) from title
Guowen Su edited Revision 18. Comment: clear mapped drives
Richard Mueller edited Revision 15. Comment: Refer to RID Master FSMO role, remove extraneous spaces
Kurt L Hudson edited Revision 10. Comment: Still trying to fix formatting - hopefully this will do it.
Kurt L Hudson edited Revision 7. Comment: Updated See Also links
Kurt L Hudson edited Revision 6. Comment: Added See Also section
Recently I had a workstation throwing the "No more connections can be made to this remote computer..." message. Turned out the clock skew between the workstation and the domain controllers was larger than the allowable Kerberos spread. Adjusting the workstation clock allowed the join process to succeed.
Hello HColeman,
I encourage you to adjust the article based on the feedback you have given. You are allowed to make modifications to the Wiki articles at any time. We highly encourage community involvement. Thanks for your feedback.
Hello,Davanand ! Can I join client or server to my domain if it has WRONG time or time zone on computer??? I've found this article and message 1398 . technet.microsoft.com/.../Cc961817 But its error appear before or after joining to domain?
You forget to add check NTLM too :p
These all are really very intresting error solutions.
Good Article.