Skip to content

Commit 2a93393

Browse files
Deland-HanDeland-Han
authored
Merge pull request #8791 from Deland-Han/ci5391
AB#5391: Error code 0x0000232A(Ensure that the domain name is typed correctly)
2 parents fbda284 + 1ce3b58 commit 2a93393

File tree

3 files changed

+88
-39
lines changed

3 files changed

+88
-39
lines changed

‎support/windows-server/active-directory/active-directory-domain-join-troubleshooting-guidance.md‎

Lines changed: 1 addition & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -77,45 +77,7 @@ For more information, see [Domain join error code 0x54b](error-code-0x54b.md).
7777

7878
### Error code 0x0000232A
7979

80-
Error 0x0000232A is logged when the client computer lacks NetBIOS name resolution to the domain.
81-
82-
:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/error-0x0000232a-message.png" alt-text="Screenshot of the dialog box showing the error message for error code 0x0000232A.":::
83-
84-
Here's an example of the error message:
85-
86-
> Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.
87-
>
88-
> The domain name "\<NetBIOS_name\>" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
89-
>
90-
> If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
91-
>
92-
> The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "\<NetBIOS_name\>":
93-
>
94-
> The error was: "DNS server failure."
95-
> (error code 0x0000232A RCODE_SERVER_FAILURE)
96-
>
97-
> The query was for the SRV record for _ldap._tcp.dc._msdcs.\<NetBIOS_name\>
98-
>
99-
> Common causes of this error include the following:
100-
>
101-
> - The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
102-
>
103-
> \<ip_address\>
104-
>
105-
> - One or more of the following zones contains incorrect delegation:
106-
>
107-
> \<NetBIOS_name\>
108-
> . (the root zone)
109-
110-
Here's an example from the *netsetup.log* file:
111-
112-
```output
113-
mm/dd/yyyy hh:mm:ss:ms NetpValidateName: checking to see if '<NetBIOS_name>' is valid as type 3 name
114-
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid for <NetBIOS_name> returned 0x54b, last error is 0x0
115-
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid [ Exists ] for '<NetBIOS_name>' returned 0x54b
116-
```
117-
118-
When you enter the domain name, make sure you enter the DNS Domain Name rather than the NetBIOS name. For example, if the DNS name of the domain is contoso.com, make sure you enter that name instead of just contoso.
80+
See [Domain join error code 0x0000232A](error-code-0x0000232a.md) for troubleshooting guide.
11981

12082
### Error code 0x3a
12183

‎support/windows-server/active-directory/error-code-0x0000232a.md‎

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
title: Domain join error code 0x0000232A
3+
description: Provides troubleshooting steps for resolving error code 0x0000232A when you join a workgroup computer to a domain.
4+
ms.date: 04/25/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: eriw,dennhu,herbertm
9+
ms.custom:
10+
- sap:active directory\on-premises active directory domain join
11+
- pcy:WinComm Directory Services
12+
---
13+
# Domain join error code 0x0000232A
14+
15+
This article provides troubleshooting steps for resolving error code 0x0000232A when you join a workgroup computer to a domain.
16+
17+
## Symptoms
18+
19+
When you join a workgroup computer to a domain, you receive the following error message:
20+
21+
> **Error code 0x0000232A**
22+
>
23+
> Computer Name/Domain Changes
24+
>
25+
> An Active Directory Domain Controller (AD DC) for the domain "\<NetBIOS\_name>" could not be contacted.
26+
>
27+
> Ensure that the domain name is typed correctly.
28+
>
29+
> If the name is correct, click Details for troubleshooting information.
30+
>
31+
> Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.
32+
>
33+
> The domain name "\<NetBIOS\_name>" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
34+
>
35+
> If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
36+
>
37+
> The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "\<NetBIOS\_name>":
38+
> The error was: "DNS server failure." (error code 0x0000232A RCODE\_SERVER\_FAILURE)
39+
>
40+
> The query was for the SRV record for \_ldap.\_tcp.dc.\_msdcs.<NetBIOS\_name>
41+
>
42+
> Common causes of this error include the following:
43+
>
44+
> * The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
45+
> \<ip\_address\>
46+
> * One or more of the following zones contains incorrect delegation:
47+
<NetBIOS\_name> . (the root zone)
48+
49+
Here's an example from the **netsetup.log** file:
50+
51+
```output
52+
NetpValidateName: checking to see if '<NetBIOS_name>' is valid as type 3 name
53+
NetpCheckDomainNameIsValid for <NetBIOS_name> returned 0x54b, last error is 0x0
54+
NetpCheckDomainNameIsValid [ Exists ] for '<NetBIOS_name>' returned 0x54b
55+
```
56+
57+
## Cause
58+
59+
Error 0x0000232A indicates that the Domain Name System (DNS) name can't be resolved. The error code can appear with error codes such as RCODE\_NAME\_ERROR and RCODE\_SERVER\_FAILURE, which indicate potential misconfigurations in the DNS settings or root hints. Error 0x0000232A might also occur if the client computer lacks NetBIOS name resolution to the domain.
60+
61+
## Troubleshooting steps
62+
63+
1. When you enter the domain name, ensure that you enter the DNS domain name rather than the NetBIOS name. For example, if the DNS name of the domain is `contoso.com`, make sure you enter that name instead of `contoso`.
64+
2. Verify the DNS server settings on the client to ensure they point to the correct DNS server.
65+
3. In the DNS management console, confirm that the SRV records are correctly registered in DNS for the Active Directory domain controller (DC).
66+
4. Conduct tests to ensure that DNS queries from the client to the Active Directory Domain Services (AD DS) server are successful after adjustments are made:
67+
68+
```console
69+
nltest /dsgetdc:
70+
```
71+
72+
The expected output should have the DC name as follows:
73+
74+
```output
75+
nltest /dsgetdc:
76+
DC: \\DC.contoso.com
77+
Address: \\<ip_address>
78+
Dom Guid: <Dom_Guid>
79+
Dom Name: contoso.com
80+
Forest Name: contoso.com
81+
Dc Site Name: Default-First-Site-Name
82+
Our Site Name: Default-First-Site-Name
83+
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE FULL_SECRET WS DS_8 DS_9
84+
The command completed successfully
85+
```

‎support/windows-server/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -359,6 +359,8 @@ items:
359359
href: ./active-directory/error-0x5-access-denied-rename-computer.md
360360
- name: Error code 0x54b
361361
href: active-directory/error-code-0x54b.md
362+
- name: Error code 0x0000232A
363+
href: active-directory/error-code-0x0000232a.md
362364
- name: Error code 0x569
363365
href: ./active-directory/error-0x569-not-granted-logon-type.md
364366
- name: Error code 0xa8b

0 commit comments

Comments
 (0)