NetpDoDomainJoin: status: 0x3a

Glenn Maxwell 11,961 Reputation points
2024-12-01T11:08:48.3066667+00:00

Hi all, I am unable to join one of my VMs to the domain. I am getting the error NetpDoDomainJoin: status: 0x3a. I don’t see any issues with my domain controller. The Test-NetConnection command to the domain controller on ports 389 and 636 is successful from the member server. Please guide me.(in the below log i have removed my domain name and used contoso). 192.168.1.100 is my dc

error-joiningdomain

PS C:\windows\system32> Test-NetConnection 192.168.1.100 -Port 389


ComputerName     : 192.168.1.100
RemoteAddress    : 192.168.1.100
RemotePort       : 389
InterfaceAlias   : Ethernet 1
SourceAddress    : 192.168.1.150
TcpTestSucceeded : True

12/01/2024 10:40:08:402 NetpDoDomainJoin
12/01/2024 10:40:08:402 NetpDoDomainJoin: using current computer names
12/01/2024 10:40:08:402 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
12/01/2024 10:40:08:402 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
12/01/2024 10:40:08:402 NetpMachineValidToJoin: 'server01'
12/01/2024 10:40:08:402 	OS Version: 10.0
12/01/2024 10:40:08:402 	Build number: 17763 (17763.rs5_release.180914-1434)
12/01/2024 10:40:08:404 	SKU: Windows Server 2019 Datacenter
12/01/2024 10:40:08:404 	Architecture: 64-bit (AMD64)
12/01/2024 10:40:08:407 NetpMachineValidToJoin: status: 0x0
12/01/2024 10:40:08:407 NetpJoinDomain
12/01/2024 10:40:08:407 	HostName: server01
12/01/2024 10:40:08:407 	NetbiosName: server01
12/01/2024 10:40:08:407 	Domain: contoso.com
12/01/2024 10:40:08:407 	MachineAccountOU: (NULL)
12/01/2024 10:40:08:407 	Account: contoso\user1
12/01/2024 10:40:08:407 	Options: 0x27
12/01/2024 10:40:08:412 NetpValidateName: checking to see if 'contoso' is valid as type 3 name
12/01/2024 10:40:08:413 NetpValidateName: 'contoso' is not a valid NetBIOS domain name: 0x7b
12/01/2024 10:40:09:126 NetpCheckDomainNameIsValid [ Exists ] for 'contoso' returned 0x0
12/01/2024 10:40:09:127 NetpValidateName: name 'contoso' is valid for type 3
12/01/2024 10:40:09:127 NetpDsGetDcName: trying to find DC in domain 'contoso', flags: 0x40001010
12/01/2024 10:40:24:123 NetpDsGetDcName: failed to find a DC having account 'server01$': 0x525, last error is 0x0
12/01/2024 10:40:24:144 NetpDsGetDcName: status of verifying DNS A record name resolution for 'dc01.contoso.com': 0x0
12/01/2024 10:40:24:145 NetpDsGetDcName: found DC '\\dc01.contoso.com' in the specified domain
12/01/2024 10:40:24:145 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
12/01/2024 10:40:24:145 NetpDisableIDNEncoding: using FQDN contoso.com from dcinfo
12/01/2024 10:40:24:152 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'contoso.com' succeeded
12/01/2024 10:40:24:152 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
12/01/2024 10:40:24:179 NetpJoinDomainOnDs: status of connecting to dc '\\dc01.contoso.com': 0x0
12/01/2024 10:40:24:179 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: contoso.com
12/01/2024 10:40:24:183 NetpProvisionComputerAccount:
12/01/2024 10:40:24:183 	lpDomain: contoso.com
12/01/2024 10:40:24:183 	lpHostName: server01
12/01/2024 10:40:24:183 	lpMachineAccountOU: (NULL)
12/01/2024 10:40:24:183 	lpDcName: dc01.contoso.com
12/01/2024 10:40:24:183 	lpMachinePassword: (null)
12/01/2024 10:40:24:183 	lpAccount: contoso\user1
12/01/2024 10:40:24:183 	lpPassword: (non-null)
12/01/2024 10:40:24:183 	dwJoinOptions: 0x27
12/01/2024 10:40:24:183 	dwOptions: 0x40000003
12/01/2024 10:40:24:188 NetpLdapBind: ldap_bind failed on dc01.contoso.com: 81: Server Down
12/01/2024 10:40:24:188 NetpJoinCreatePackagePart: status:0x3a.
12/01/2024 10:40:24:188 NetpJoinDomainOnDs: Function exits with status of: 0x3a
12/01/2024 10:40:24:189 NetpJoinDomainOnDs: status of disconnecting from '\\dc01.contoso.com': 0x0
12/01/2024 10:40:24:194 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'contoso.com' returned 0x0
12/01/2024 10:40:24:195 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'contoso.com': 0x0
12/01/2024 10:40:24:195 NetpDoDomainJoin: status: 0x3a

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,844 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,545 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,468 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,762 questions
Windows Server Infrastructure
Windows Server Infrastructure
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Infrastructure: A Microsoft solution area focused on providing organizations with a cloud solution that supports their real-world needs and meets evolving regulatory requirements.
556 questions
0 comments No comments
{count} votes

Accepted answer
  1. Daisy Zhou 26,806 Reputation points Microsoft Vendor
    2024-12-03T07:34:28.76+00:00

    Hello Glenn Maxwell,

    Thank you for posting in Q&A forum.

    The error code 0x3a typically indicates that the specified server cannot perform the required operation. Here are a few steps you can take to troubleshoot this issue:

    1. Ensure that the DNS server addresses are correct. Verify that there are no stale or duplicate DNS records referencing the same computer account. Make sure the domain name, domain controllers (DCs), and DNS servers can be pinged.
    2. Review Netsetup.log:The Netsetup.log file, located at C:\Windows\Debug\netsetup.log, can provide detailed information about the domain join process and any errors encountered.
    3. Verify the connectivity between the client being joined and the target DC over the required ports and protocols. Ensure that no network devices (like routers, firewalls, or VPNs) are blocking the necessary traffic.
    4. Ensure that NetBIOS over TCP/IP is enabled. You can check this by going to the properties of your network connection, selecting Internet Protocol Version 4 (TCP/IPv4), and then clicking on Properties.

    References:

    Active Directory domain join troubleshooting guidance

    I hope the information above is helpful.

    If you have any questions or concerns, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.