Skip to content

Commit 3970ae5

Browse files
v-liannav-lianna
committed
AB#5708 Split article into two separate articles
1 parent d236832 commit 3970ae5

3 files changed

Lines changed: 231 additions & 0 deletions

File tree

‎support/windows-server/active-directory/domain-join-authentication-errors.md‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
title: Troubleshoot Authentication errors that occur when you join Windows-based computers to a domain
3+
description: Troubleshooting guide for Authentication related error messages that occurs when you join Windows-based computers to a domain.
4+
ms.date: 05/08/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika
9+
ms.custom:
10+
- sap:active directory\on-premises active directory domain join
11+
- pcy:WinComm Directory Services
12+
---
13+
# Troubleshoot Authentication errors that occur when you join Windows-based computers to a domain
14+
15+
This article describes several Authentication related error messages that can occur when you join client computers that are running Windows to a domain. This article also provides troubleshooting suggestions for these errors.
16+
17+
## Where to find the Netsetup.log file
18+
19+
Netsetup log file contains most information about domain join activities. The file is located on the client machine at %windir%\\debug\\Netsetup.log file. This log file is enabled by default. No need to explicitly enable it.
20+
21+
## You have exceeded the maximum number of computer accounts you are allowed to create in this domain.
22+
23+
### Resolution
24+
25+
Make sure that you have permissions to add computers to the domain, and that you have not exceeded the quota that is defined by your Domain Administrator.
26+
27+
To join a computer to the domain, the user account must be granted **Create computer object** permissions in Active Directory.
28+
29+
> [!Note]
30+
> By default, a non-administrator user can join a maximum of 10 computers to an Active Directory domain.
31+
32+
## Logon failure: The target account name is incorrect.
33+
34+
### Resolution
35+
36+
Check that the domain controllers (DCs) are registered by using correct IP addresses on the DNS server, and that their Service Principal Names (SPNs) are registered correctly in their Active Directory accounts.
37+
38+
## Logon failure: the user has not been granted the requested logon type at this computer.
39+
40+
### Resolution
41+
42+
Make sure that you have permissions to add computers to the domain. To join a computer to the domain, the user account must be granted the **Create computer object** permission in Active Directory.
43+
44+
Additionally, make sure that the specified user account is allowed to log on locally to the client computer. To do this, configure the **Allow log on locally** setting in Group Policy under **Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment**.
45+
46+
## Logon failure: unknown user name or bad password.
47+
48+
### Resolution
49+
50+
Make sure that you use the correct user name and password combination of an existing Active Directory user account when you are prompted for credentials to add the computer to the domain.
51+
52+
## No mapping between account names and security IDs was done.
53+
54+
### Resolution
55+
56+
This error is likely a transient error that is logged when a domain join searches the target domain to determine whether a matching computer account was already created or whether the join operation has to dynamically create a computer account on the target domain.
57+
58+
## Not enough storage is available to complete this operation.
59+
60+
### Resolution
61+
62+
This error can occur when the Kerberos token size is larger than the maximum default size. If this situation, you have to increase the Kerberos token size of the computer that you try to join to the domain. For more information, see the following Knowledge Base articles:
63+
[935744 "Not enough storage is available to complete this operation" error message when you use a domain controller to join a computer to a domain](../../windows-client/windows-security/not-enough-storage-available-complete-operation-error.md)
64+
[327825 Problems with Kerberos authentication when a user belongs to many groups](../windows-security/kerberos-authentication-problems-if-user-belongs-to-groups.md)
65+
66+
## The account is not authorized to login from this station.
67+
68+
### Resolution
69+
70+
This problem is related to mismatched SMB Signing settings between the client computer and the DC that is being contacted for the domain join operation. Review the following documentation to further investigate the current and recommended values in your environment:
71+
[281648 Error message: The account is not authorized to login from this station](account-not-authorized-login-from-this-station.md)
72+
[823659 Client, service, and program issues can occur if you change security settings and user rights assignments](https://support.microsoft.com/help/823659/client-service-and-program-issues-can-occur-if-you-change-security-set)
73+
74+
## The account specified for this service is different from the account specified for other services running in the same process.
75+
76+
### Resolution
77+
78+
Make sure that the DC through which you are trying to join the domain has the Windows Time service started.

‎support/windows-server/active-directory/domain-join-networking-errors.md‎

Lines changed: 149 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,149 @@
1+
---
2+
title: Troubleshoot Networking errors that occur when you join Windows-based computers to a domain
3+
description: Troubleshooting guide for Networking related error messages that occurs when you join Windows-based computers to a domain.
4+
ms.date: 05/08/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika
9+
ms.custom:
10+
- sap:active directory\on-premises active directory domain join
11+
- pcy:WinComm Directory Services
12+
---
13+
# Troubleshoot Networking errors that occur when you join Windows-based computers to a domain
14+
15+
This article describes several Networking related error messages that can occur when you join client computers that are running Windows to a domain. This article also provides troubleshooting suggestions for these errors.
16+
17+
## Where to find the Netsetup.log file
18+
19+
Netsetup log file contains most information about domain join activities. The file is located on the client machine at %windir%\\debug\\Netsetup.log file. This log file is enabled by default. No need to explicitly enable it.
20+
21+
## 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.
22+
23+
### Resolution
24+
25+
When you type the domain name, make sure that you type the Domain Name System (DNS) name and not the Network Basic Input/Output System (NetBIOS) name. For example, if the DNS name of the target domain is `contoso.com`, make sure that you enter `contoso.com` instead of the NetBIOS domain name of "contoso."
26+
27+
Additionally, verify that the computer can reach a DNS server that hosts the DNS zone of the target domain or can resolve DNS names in that domain. Make sure that the correct DNS server is configured on this client as the preferred DNS, and that the client has connectivity to that server. To verify this, you can run one of the following commands:
28+
29+
```console
30+
nltest /dsgetdc:<netbios domain name> /force
31+
```
32+
33+
```console
34+
nltest /dsgetdc:<DNS domain name> /force
35+
```
36+
37+
## 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.
38+
39+
### Resolution
40+
41+
When you type the domain name, make sure that you type the DNS name and not the NetBIOS name.
42+
43+
Additionally, verify that the computer can reach a DNS server that hosts the DNS zone of the target domain or can resolve DNS names in that domain. Make sure that the correct DNS server is configured on this client as the preferred DNS, and that the client has connectivity to that server. To verify this, you can run one of the following commands:
44+
45+
```console
46+
nltest /dsgetdc:<netbios domain name> /force
47+
```
48+
49+
```console
50+
nltest /dsgetdc:<DNS domain name> /force
51+
```
52+
53+
## An operation was attempted on a nonexistent network connection.
54+
55+
### Resolution
56+
57+
When you type the domain name, make sure that you type the DNS name and not the NetBIOS name.
58+
Additionally, restart the computer before you try to join the computer to the domain.
59+
60+
## 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.
61+
62+
### Resolution
63+
64+
Restart the computer that you are trying to join to the domain to make sure that there are no latent connections to any of the domain servers.
65+
66+
When you type the domain name, make sure that you type the DNS name and not the NetBIOS name.
67+
68+
## Network name cannot be found.
69+
70+
### Resolution
71+
72+
Verify that the computer can reach a DNS server that hosts the DNS zone of the target domain or can resolve DNS names in that domain. Make sure that the correct DNS server has been configured on this client as the preferred DNS, and that the client has connectivity to that server. To verify this, you can run one of the following commands:
73+
74+
```console
75+
nltest /dsgetdc:<netbios domain name> /force
76+
```
77+
78+
```console
79+
nltest /dsgetdc:<DNS domain name> /force
80+
```
81+
82+
When you type the domain name, make sure that you type the DNS name and not the NetBIOS name.
83+
84+
Additionally, you can update the network adapter driver.
85+
86+
## 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.
87+
88+
### Resolution
89+
90+
Before joining the computer to the domain, make sure that you have cleared all mapped connections to any drives.
91+
92+
Restart the computer that you are trying to join to the domain to make sure that there are no latent connections to any of the domain servers.
93+
94+
When you type the domain name, make sure that you type the DNS name and not the NetBIOS name.
95+
96+
The error may be transient. Try again later. If the issue persists, verify the status of the DC that the client is connecting to (active connections, network connectivity, and so on). You may want to restart the DC if the issue persists.
97+
98+
## The format of the specified network name is invalid.
99+
100+
### Resolution
101+
102+
Verify that the computer can reach a DNS server that hosts the DNS zone of the target domain or can resolve DNS names in that domain. Make sure that the correct DNS server has been configured on this client as the preferred DNS, and that the client has connectivity to that server. To verify this, you can run one of the following commands:
103+
104+
```console
105+
nltest /dsgetdc:<netbios domain name> /force
106+
```
107+
108+
```console
109+
nltest /dsgetdc:<DNS domain name> /force
110+
```
111+
112+
When you type the domain name, make sure that you type the DNS name and not the NetBIOS name. Make sure that you have the most up-to-date drivers installed for the client computer's network adapter. Verify connectivity between the client that is being joined and the target DC over the required ports and protocols. Disable the **TCP** **Chimney** offload feature and IP offloading.
113+
114+
## The directory service has exhausted the pool of relative identifiers.
115+
116+
### Resolution
117+
118+
Make sure that the DC that hosts the relative ID (RID) operations master is online and functional. For more information, see [Event ID 16650: The account-identifier allocator failed to initialize in Windows Server](event-16650-account-identifier-allocator-not-initialize.md).
119+
120+
> [!Note]
121+
> You can use the `netdom query fsmo` command to determine which DC has the RID Master role.
122+
123+
Verify that Active Directory is replicating between all DCs. You can use the following command to detect any errors:
124+
125+
```console
126+
repadmin /replsummary /bysrc /bydest /sort:delta
127+
```
128+
129+
## The remote procedure call failed and did not execute.
130+
131+
### Resolution
132+
133+
Make sure that you have the most up-to-date drivers installed for the client computer's network adapter. Verify connectivity between the client that is being joined and the target DC over the required ports and protocols. Disable the **TCP Chimney** offload feature and IP offloading.
134+
135+
This problem can also be caused by one of the following conditions:
136+
137+
- A network device (router, firewall, or VPN device) is blocking connectivity over the ports and protocols that are used by the MSRPC protocol.
138+
- A network device (router, firewall, or VPN device) is rejecting network packets between the client that is being joined and the DC.
139+
140+
> [!NOTE]
141+
> The following articles contain port requirement information:
142+
[832017 Service overview and network port requirements for Windows](../networking/service-overview-and-network-port-requirements.md)
143+
[179442 How to configure a firewall for domains and trusts](config-firewall-for-ad-domains-and-trusts.md)
144+
145+
## Changing the Primary Domain DNS name of this computer to "" failed. The name will remain ".".The specified server cannot perform the operation.
146+
147+
### Resolution
148+
149+
This error occurs when you use the domain join 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 fix this error, see [2018583 Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."](https://support.microsoft.com/help/2018583/windows-7-or-windows-server-2008-r2-domain-join-displays-error-changin).

‎support/windows-server/toc.yml‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -381,6 +381,10 @@ items:
381381
href: ./active-directory/support-for-active-directory-over-nat.md
382382
- name: '"The account is not authorized to login from this station" error'
383383
href: ./active-directory/account-not-authorized-login-from-this-station.md
384+
- name: Troubleshoot authentication errors when joining computers to a domain
385+
href: ./active-directory/domain-join-authentication-errors.md
386+
- name: Troubleshoot networking errors when joining computers to a domain
387+
href: ./active-directory/domain-join-networking-errors.md
384388
- name: Troubleshoot errors when joining computers to a domain
385389
href: ./active-directory/troubleshoot-errors-join-computer-to-domain.md
386390
- name: LDAP configuration and interoperability

0 commit comments

Comments
 (0)