Skip to content

Commit 5f8dd30

Browse files
Deland-HanDeland-Han
committed
update with edits
1 parent f13c8f4 commit 5f8dd30

3 files changed

Lines changed: 89 additions & 41 deletions

File tree

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

Lines changed: 2 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Make sure of the following items:
7979

8080
### Error code 0x6D9
8181

82-
See [Domain join error 0x6D9 "There are no more endpoints available from the endpoint mapper"](./domain-join-error-0x6d9-there-are-no-more-endpoints-available-from-the-endpoint-mapper.md) for troubleshooting guide.
82+
See [Domain join error 0x6D9 "There are no more endpoints available from the endpoint mapper"](./domain-join-error-0x6d9-there-are-no-more-endpoints-available-from-the-endpoint-mapper.md) for troubleshooting guide.
8383

8484
### Error code 0xa8b
8585

@@ -176,45 +176,7 @@ To resolve the 0x54b error, follow these steps:
176176

177177
### Error code 0x0000232A
178178

179-
Error 0x0000232A is logged when the client computer lacks NetBIOS name resolution to the domain.
180-
181-
:::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.":::
182-
183-
Here's an example of the error message:
184-
185-
> 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.
186-
>
187-
> 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.
188-
>
189-
> If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
190-
>
191-
> 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\>":
192-
>
193-
> The error was: "DNS server failure."
194-
> (error code 0x0000232A RCODE_SERVER_FAILURE)
195-
>
196-
> The query was for the SRV record for _ldap._tcp.dc._msdcs.\<NetBIOS_name\>
197-
>
198-
> Common causes of this error include the following:
199-
>
200-
> - The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
201-
>
202-
> \<ip_address\>
203-
>
204-
> - One or more of the following zones contains incorrect delegation:
205-
>
206-
> \<NetBIOS_name\>
207-
> . (the root zone)
208-
209-
Here's an example from the *netsetup.log* file:
210-
211-
```output
212-
mm/dd/yyyy hh:mm:ss:ms NetpValidateName: checking to see if '<NetBIOS_name>' is valid as type 3 name
213-
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid for <NetBIOS_name> returned 0x54b, last error is 0x0
214-
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid [ Exists ] for '<NetBIOS_name>' returned 0x54b
215-
```
216-
217-
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.
179+
See [Domain join error code 0x0000232A](error-code-0x0000232a.md) for troubleshooting guide.
218180

219181
### Error code 0x3a
220182

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

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
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+
> An Active Directory Domain Controller (AD DC) for the domain "\<NetBIOS\_name>" could not be contacted.
25+
>
26+
> Ensure that the domain name is typed correctly.
27+
>
28+
> If the name is correct, click Details for troubleshooting information.
29+
>
30+
> 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.
31+
>
32+
> 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.
33+
>
34+
> If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
35+
>
36+
> 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>":
37+
> The error was: "DNS server failure." (error code 0x0000232A RCODE\_SERVER\_FAILURE)
38+
>
39+
> The query was for the SRV record for \_ldap.\_tcp.dc.\_msdcs.<NetBIOS\_name>
40+
>
41+
> Common causes of this error include the following:
42+
>
43+
> * The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
44+
> \<ip\_address\>
45+
> * One or more of the following zones contains incorrect delegation:
46+
<NetBIOS\_name> . (the root zone)
47+
48+
Here's an example from the *netsetup.log* file:
49+
50+
```output
51+
mm/dd/yyyy hh:mm:ss:ms NetpValidateName: checking to see if '<NetBIOS\_name>' is valid as type 3 name
52+
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid for <NetBIOS\_name> returned 0x54b, last error is 0x0
53+
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid [ Exists ] for '<NetBIOS\_name>' returned 0x54b
54+
```
55+
56+
## Cause
57+
58+
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 DNS settings or root hints. Error 0x0000232A might also occur if the client computer lacks NetBIOS name resolution to the domain.
59+
60+
## Troubleshooting steps
61+
62+
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.
63+
2. Verified the DNS server settings on the client to ensure they're pointing to the correct DNS server.
64+
3. In DNS management console, confirm that SRV records are correctly registered in DNS for the Active Directory Domain Controller.
65+
4. Conducted tests to ensure that DNS queries from the client to the AD DS server are successful after adjustments are made.
66+
67+
```console
68+
nltest /dsgetdc:
69+
```
70+
71+
The expected output should have the DC name as following.
72+
73+
```output
74+
nltest /dsgetdc:
75+
DC: \\DC.contoso.com
76+
Address: \\<ip_address>
77+
Dom Guid: ceb4e2e5-df9b-4b34-ab6f-82777445806b
78+
Dom Name: contoso.com
79+
Forest Name: contoso.com
80+
Dc Site Name: Default-First-Site-Name
81+
Our Site Name: Default-First-Site-Name
82+
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE FULL_SECRET WS DS_8 DS_9
83+
The command completed successfully
84+
```

‎support/windows-server/toc.yml‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -349,12 +349,14 @@ items:
349349
href: ./active-directory/cannot-connect-internet-domain.md
350350
- name: Default limit to workstation numbers
351351
href: ./active-directory/default-workstation-numbers-join-domain.md
352-
- name: 'Error 0x6D9 "No more endpoints available from the endpoint mapper"'
352+
- name: Error 0x6D9 "No more endpoints available from the endpoint mapper"
353353
href: ./active-directory/domain-join-error-0x6d9-there-are-no-more-endpoints-available-from-the-endpoint-mapper.md
354354
- name: Failure when you use an existing computer account to join a domain
355355
href: ./active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain.md
356356
- name: Error 0x5 Access Denied when you rename a computer
357357
href: ./active-directory/error-0x5-access-denied-rename-computer.md
358+
- name: Error code 0x0000232A
359+
href: active-directory/error-code-0x0000232a.md
358360
- name: Error code 0x569
359361
href: ./active-directory/error-0x569-not-granted-logon-type.md
360362
- name: Error code 0xa8b

0 commit comments

Comments
 (0)