Skip to content

Commit c293c7d

Browse files
v-liannav-lianna
committed
Create status-code-0x6ba-rpc-server-unavailable.md
1 parent 18bfc0b commit c293c7d

1 file changed

Lines changed: 124 additions & 0 deletions

File tree

‎support/windows-server/active-directory/status-code-0x6ba-rpc-server-unavailable.md‎

Lines changed: 124 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,124 @@
1+
---
2+
title: Status Code 0x6ba And The RPC Server Is Unavailable
3+
description: Provides troubleshooting steps for resolving the remote procedure call (RPC) status code 0x6ba when you join a workgroup computer to a domain.
4+
ms.date: 04/18/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, raviks, herbertm, dennhu, eriw, v-lianna
9+
ms.custom:
10+
- sap:active directory\on-premises active directory domain join
11+
- pcy:WinComm Directory Services
12+
---
13+
# Status code 0x6ba: The RPC server is unavailable
14+
15+
This article provides troubleshooting steps for resolving the remote procedure call (RPC) status code 0x6ba when you join a workgroup computer to a domain.
16+
17+
When you join a workgroup computer to a domain, you receive the following error message:
18+
19+
> Changing the Primary Domain DNS name of this computer to "" failed. The name will remain "\<DomainName\>".
20+
> The error was:
21+
> The RPC service is unavailable.
22+
23+
Here's more information about the error code:
24+
25+
|Hexadecimal error |Decimal error |Symbolic error string |Error description |
26+
|---------|---------|---------|---------|
27+
|0x6ba |1722 |RPC_S_SERVER_UNAVAILABLE |The RPC server is unavailable. |
28+
29+
When you check the NetSetup.log file, you see the following entries. For example:
30+
31+
```output
32+
NetpGetComputerObjectDn: Unable to bind to DS on '\\DCNAME': 0x6ba
33+
NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x6ba
34+
NetpProvisionComputerAccount: LDAP creation failed: 0x6ba
35+
ldap_unbind status: 0x0
36+
NetpJoinCreatePackagePart: status:0x6ba.
37+
NetpJoinDomainOnDs: Function exits with status of: 0x6ba
38+
NetpJoinDomainOnDs: status of disconnecting from '\\DCNAME': 0x0
39+
NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'DOMAINNAME' returned 0x0
40+
NetpJoinDomainOnDs: NetpResetIDNEncoding on 'DOMAINNAME': 0x0
41+
NetpDoDomainJoin: status: 0x6ba
42+
```
43+
44+
## Troubleshoot the connection issue
45+
46+
To troubleshoot this issue, use the following steps:
47+
48+
1. Check the **NetSetup.log** file (**C:\\Windows\\Debug\\NetSetup.log**) on the client machine, and confirm if the domain controller (DC) locator process has successfully located a DC. However, the client machine fails to bind to the DC with status code 0x6ba. For example:
49+
50+
```output
51+
NetpJoinDomainOnDs: status of connecting to dc '\\DCNAME': 0x0
52+
NetpGetComputerObjectDn: Unable to bind to DS on '\\DCNAME': 0x6ba
53+
```
54+
55+
2. Make sure the network ports aren't blocked by a firewall or third-party application which is listening on the required ports of the DC (identified in step 1).
56+
57+
The endpoint mapper (listening on port 135) tells the client which randomly assigned port a service is listening on. Check the following ports:
58+
59+
|Server port |Service/Protocol |
60+
|---------|---------|
61+
|Transmission Control Protocol (TCP) 135 |RPC Endpoint Mapper |
62+
|TCP 49152 - 65535 |RPC (dynamic ports allocation) |
63+
|TCP 445 |Server Message Block (SMB) |
64+
|User Datagram Protocol (UDP)/TCP 389 |Lightweight Directory Access Protocol (LDAP) |
65+
66+
Refer to the list of required ports in [How to configure a firewall for Active Directory domains and trusts](config-firewall-for-ad-domains-and-trusts.md).
67+
68+
3. Identify if a port is blocked on a DC by using the [PortQry](https://www.microsoft.com/download/details.aspx?id=17148) command-line tool. For more information, see [Using the PortQry command-line tool](../networking/portqry-command-line-port-scanner-v2.md)
69+
70+
Here are some example syntaxes:
71+
72+
> [!NOTE]
73+
> Replace \<problem_server\> with the DC name identified in step 1.
74+
75+
- `portqry -n <problem_server> -e 135`
76+
- `portqry -n <problem_server> -e 445`
77+
- `portqry -n <problem_server> -e 389`
78+
- `portqry -n <problem_server> -p UDP -e 389`
79+
- `portqry -n <problem_server> -r 49152:65535`
80+
81+
Here are some example outputs:
82+
83+
If the connection to TCP 135 port on the DC is blocked, you see the following output:
84+
85+
```output
86+
C:\PortQryV2>portqry -n dc2 -e 135
87+
Querying target system called:
88+
Dc2
89+
Attempting to resolve name to IP address…
90+
Name resolved to 192.168.1.2
91+
querying...
92+
TCP port 135 <epmap service>: FILTERED
93+
```
94+
If the connection to TCP 389 port on the DC is successful, you see the following output:
95+
96+
```output
97+
C:\PortQryV2>portqry -n dc2 -e 389
98+
Querying target system called:
99+
Dc2
100+
Attempting to resolve name to IP address…
101+
Name resolved to 192.168.1.2
102+
querying...
103+
TCP port 389 <ldap service>: LISTENING
104+
```
105+
106+
4. Collect [network monitor](https://www.microsoft.com/download/details.aspx?id=4865) trace when reproducing the issue to double check the network connectivity.
107+
108+
For example, the following network trace collected by the PortQry command-line tool might indicate there's a network connectivity issue from the client machine to the DC's TCP 135 port (RPC).
109+
110+
```output
111+
PortQry.exe CLIENT DC TCP TCP:Flags=CE....S., SrcPort=51542, DstPort=DCE endpoint resolution(135), PayloadLen=0, Seq=4232829278, Ack=0, Win=8192 ( Negotiating scale factor 0x8 ) = 8192 {TCP:16, IPv4:15}
112+
PortQry.exe CLIENT DC TCP TCP:[SynReTransmit #50]Flags=CE....S., SrcPort=51542, DstPort=DCE endpoint resolution(135), PayloadLen=0, Seq=4232829278, Ack=0, Win=8192 ( Negotiating scale factor 0x8 ) = 8192 {TCP:16, IPv4:15}
113+
PortQry.exe CLIENT DC TCP TCP:[SynReTransmit #50]Flags=......S., SrcPort=51542, DstPort=DCE endpoint resolution(135), PayloadLen=0, Seq=4232829278, Ack=0, Win=8192 ( Negotiating scale factor 0x8 ) = 8192 {TCP:16, IPv4:15}
114+
In the network trace collected on the client side, you see the retransmit package of TCP SYN to DC's TCP 135 port. And no response is received from DC.
115+
In the network trace collected on the DC side, you might not see the TCP SYN package from the client. It might be blocked by a firewall or middle device.
116+
```
117+
118+
5. Check the network device and firewall between the client and the DC to further investigate the network connectivity issue if necessary.
119+
120+
## More information
121+
122+
- [How to configure a firewall for Active Directory domains and trusts](config-firewall-for-ad-domains-and-trusts.md)
123+
- [Locating Active Directory domain controllers in Windows and Windows Server](/windows-server/identity/ad-ds/manage/dc-locator?tabs=dns-based-discovery)
124+
- [Troubleshoot domain controller location issues in Windows](../windows-security/troubleshoot-domain-controller-location-issues.md)

0 commit comments

Comments
 (0)