Troubleshooting Domain Join Error Messages

Troubleshooting Domain Join Error Messages


This article describes some of the common domain join error messages and possible steps that need to be performed when you encounter these errors joining a client machine (server or workstation) to a domain.


In the table below, you will find error messages associated with domain join and possible resolution(s).

 Domain Join Error

 Resolution

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.

When you type the domain name, make sure you type the DNS Domain Name, rather than the NetBIOS name.  For example, if the DNS name of the domain is fabrikam.com, make sure you enter that name instead of just fabrikam.

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.

Run nslookup, and verify that the machine can reach the DNS server.  Ensure that the correct DNS server is specified and you have connectivity to that server.

Make sure you configured right preferred DNS IP in client, which one is the domain controller IP.

An operation was attempted on a nonexistent network connection.

When you type the domain name, make sure you type the DNS Domain Name, rather than the NetBIOS name.  For example, if the DNS name of the domain is fabrikam.com, make sure you enter that name instead of just fabrikam.

You have exceeded the maximum number of computer accounts you are allowed to create in this domain.

Ensure that you have permissions to add computers to the domain or that you have not exceeded the quota limit defined by your Domain Administrator.

Logon failure: The target account name is incorrect.

Run nslookup, and verify that the machine can reach the DNS server.  Ensure that the correct DNS server is specified and you have connectivity to that server.

Logon failure: the user has not been granted the requested logon type at this computer.

Ensure that you have permissions to add computers to the domain.

Logon failure: unknown user name or bad password.

Ensure that you are using the correct user name\password combination when prompted for credentials to add the computer to the domain.

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.

  • Reboot the machine you are trying to join to the domain to ensure there are no latent connections to any of the domain servers.
  • When you type the domain name, make sure you type the DNS Domain Name, rather than the NetBIOS name.  For example, if the DNS name of the domain is fabrikam.com, make sure you enter that name instead of just fabrikam.

Network name cannot be found.

  • Run nslookup, and verify that the machine can reach the DNS server.  Ensure that the correct DNS server is specified and you have connectivity to that server.
  • Update the network card driver.

No mapping between account names and security IDs was done.

  • Ensure that you are using the correct user name\password combination when prompted for credentials to add the computer to the domain.
  • Ensure that you entered the correct DNS Domain name for domain you are trying to join.

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.

Before joining the computer to the domain, ensure that you have cleared all mapped connections to any drives. Net del

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 is not authorized to login from the station. You must edit the SMB value in the registry.  For more information on this topic see:

The account specified for this service is different from the account specified for other services running in the same process.

Ensure that the domain controller through which you are trying to perform the domain join has the Windows Time service started. 

The directory service has exhausted the pool of relative identifiers.

Ensure that the domain controller hosting the RID Master FSMO role is online and functional.  
 The format of the specified network name is invalid.
  • Run nslookup, and verify that the machine can reach the DNS server.  Ensure that the correct DNS server is specified and you have connectivity to that server.
  • When you type the domain name, make sure you type the DNS Domain Name, rather than the NetBIOS name.  For example, if the DNS name of the domain is fabrikam.com, make sure you enter that name instead of just fabrikam.
 The remote procedure call failed and did not execute. Ensure you have the most up to date drivers for the client machine’s network adapter.
 Changing the Primary Domain DNS name of this computer to "" failed. The name will remain "<DNS domain>.<top level domain>".The specified server cannot perform the operation. This error occurs when using the domain join user interface (UI) to join a Windows 7 or Windows Server 2008 R2 workgroup computer to an Active Directory domain by specifying the target DNS domain. To resolve this error message follow the actions outlined in KB 2018583.


See Also

Sort by: Published Date | Most Recent | Most Useful
Comments
  • 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.

Page 1 of 1 (6 items)