Skip to content

Commit f65b076

Browse files
Deland-HanDeland-Han
committed
update
1 parent 5180754 commit f65b076

4 files changed

Lines changed: 109 additions & 110 deletions

‎support/windows-server/active-directory/domain-join-error-0x40-the-specified-network-name-is-no-longer-available.md‎

Lines changed: 26 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -74,33 +74,34 @@ The issue is related to Server Message Block (SMB).
7474

7575
#### Example
7676

77-
The following is an example of a network trace and its analysis:
77+
The following is an example of a network trace:
7878

7979
```output
80-
CLIENT1 DC1.ADATUM.COM TCP TCP:Flags=......S., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=0, Seq=1299628969, Ack=0, Win=8192 ( ) = 8192 {TCP:267, IPv4:5}
81-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A..S., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785282675, Ack=1299628970, Win=8192 ( Scale factor not supported ) = 8192 {TCP:267, IPv4:5}
82-
CLIENT1 DC1.ADATUM.COM TCP TCP:Flags=...A...., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=0, Seq=1299628970, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
83-
CLIENT1 DC1.ADATUM.COM KerberosV5 KerberosV5:TGS Request Realm: ADATUM.COM Sname: cifs/DC1.ADATUM.COM {TCP:267, IPv4:5}
84-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785282676, Ack=1299628970, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
85-
CLIENT1 DC1.ADATUM.COM TCP TCP:[ReTransmit #1539]Flags=...A...., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=1460, Seq=1299628970 - 1299630430, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
86-
CLIENT1 DC1.ADATUM.COM TCP TCP:[ReTransmit #1539]Flags=...A...., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=1460, Seq=1299628970 - 1299630430, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
87-
CLIENT1 DC1.ADATUM.COM TCP TCP:[ReTransmit #1539]Flags=...A...., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=536, Seq=1299628970 - 1299629506, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
88-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785282676, Ack=1299629506, Win=63704 (scale factor 0x0) = 63704 {TCP:267, IPv4:5}
89-
CLIENT1 DC1.ADATUM.COM TCP TCP:[Continuation to #0]Flags=...A...., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=536, Seq=1299629506 - 1299630042, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
90-
CLIENT1 DC1.ADATUM.COM TCP TCP:[Continuation to #0]Flags=...A...., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=536, Seq=1299630042 - 1299630578, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
91-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785282676, Ack=1299630042, Win=63168 (scale factor 0x0) = 63168 {TCP:267, IPv4:5}
92-
CLIENT1 DC1.ADATUM.COM TCP TCP:[Continuation to #0]Flags=...AP..., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=536, Seq=1299630578 - 1299631114, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
93-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785282676, Ack=1299630738, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
94-
CLIENT1 DC1.ADATUM.COM KerberosV5 KerberosV5: {TCP:267, IPv4:5}
95-
DC1.ADATUM.COM CLIENT1 TCP TCP:[Continuation to #0]Flags=...AP..., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=290, Seq=2785284136 - 2785284426, Ack=1299630738, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
96-
CLIENT1 DC1.ADATUM.COM TCP TCP:Flags=...A...., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=0, Seq=1299632186, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
97-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785284426, Ack=1299631114, Win=63864 (scale factor 0x0) = 63864 {TCP:267, IPv4:5}
98-
CLIENT1 DC1.ADATUM.COM TCP TCP:[Continuation to #1552]Flags=...AP..., SrcPort=59259, DstPort=Kerberos(88), PayloadLen=320, Seq=1299632186 - 1299632506, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
99-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785284426, Ack=1299632186, Win=62792 (scale factor 0x0) = 62792 {TCP:267, IPv4:5}
100-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785284426, Ack=1299632506, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
101-
CLIENT1 DC1.ADATUM.COM TCP TCP:Flags=...A...F, SrcPort=59259, DstPort=Kerberos(88), PayloadLen=0, Seq=1299632506, Ack=2785282676, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
102-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A...., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785284136, Ack=1299632507, Win=64240 (scale factor 0x0) = 64240 {TCP:267, IPv4:5}
103-
DC1.ADATUM.COM CLIENT1 TCP TCP:Flags=...A.R.., SrcPort=Kerberos(88), DstPort=59259, PayloadLen=0, Seq=2785284136, Ack=1299632507, Win=0 (scale factor 0x0) = 0
80+
Source Destination Protocol Info
81+
CLIENT1 DC1.ADATUM.COM TCP 59259 → 88 [SYN] Seq=1299628969 Win=8192 Len=0
82+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [SYN, ACK] Seq=2785282675 Ack=1299628970 Win=8192 Len=0
83+
CLIENT1 DC1.ADATUM.COM TCP 59259 → 88 [ACK] Seq=1299628970 Ack=2785282676 Win=64240 Len=0
84+
CLIENT1 DC1.ADATUM.COM Kerberos TGS-REQ Realm: ADATUM.COM Sname: cifs/DC1.ADATUM.COM
85+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785282676 Ack=1299628970 Win=64240 Len=0
86+
CLIENT1 DC1.ADATUM.COM TCP [ReTransmit] 59259 → 88 [ACK] Seq=1299628970 Ack=2785282676 Win=64240 Len=1460
87+
CLIENT1 DC1.ADATUM.COM TCP [ReTransmit] 59259 → 88 [ACK] Seq=1299628970 Ack=2785282676 Win=64240 Len=1460
88+
CLIENT1 DC1.ADATUM.COM TCP [ReTransmit] 59259 → 88 [ACK] Seq=1299628970 Ack=2785282676 Win=64240 Len=536
89+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785282676 Ack=1299629506 Win=63704 Len=0
90+
CLIENT1 DC1.ADATUM.COM TCP [Continuation] 59259 → 88 [ACK] Seq=1299629506 Ack=2785282676 Win=64240 Len=536
91+
CLIENT1 DC1.ADATUM.COM TCP [Continuation] 59259 → 88 [ACK] Seq=1299630042 Ack=2785282676 Win=64240 Len=536
92+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785282676 Ack=1299630042 Win=63168 Len=0
93+
CLIENT1 DC1.ADATUM.COM TCP [Continuation] 59259 → 88 [PSH, ACK] Seq=1299630578 Ack=2785282676 Win=64240 Len=536
94+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785282676 Ack=1299630738 Win=64240 Len=0
95+
CLIENT1 DC1.ADATUM.COM Kerberos KerberosV5 Message
96+
DC1.ADATUM.COM CLIENT1 TCP [Continuation] 88 → 59259 [PSH, ACK] Seq=2785284136 Ack=1299630738 Win=64240 Len=290
97+
CLIENT1 DC1.ADATUM.COM TCP 59259 → 88 [ACK] Seq=1299632186 Ack=2785282676 Win=64240 Len=0
98+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785284426 Ack=1299631114 Win=63864 Len=0
99+
CLIENT1 DC1.ADATUM.COM TCP [Continuation] 59259 → 88 [PSH, ACK] Seq=1299632186 Ack=2785282676 Win=64240 Len=320
100+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785284426 Ack=1299632186 Win=62792 Len=0
101+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785284426 Ack=1299632506 Win=64240 Len=0
102+
CLIENT1 DC1.ADATUM.COM TCP 59259 → 88 [FIN, ACK] Seq=1299632506 Ack=2785282676 Win=64240 Len=0
103+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [ACK] Seq=2785284136 Ack=1299632507 Win=64240 Len=0
104+
DC1.ADATUM.COM CLIENT1 TCP 88 → 59259 [RST, ACK] Seq=2785284136 Ack=1299632507 Win=0 Len=0
104105
```
105106

106107
From the trace, we can find the Domain Controller (DC) doesn't respond to the Ticket Granting Service (TGS) request from the client for the Service Principal Name (SPN) CIFS/DC1.ADATUM.COM. It sends back a Transmission Control Protocol (TCP) acknowledgment, which suggests the DC received the TGS request. However, it doesn't reply with a valid TGS Response. Finally, the client terminates the TCP connection.

‎support/windows-server/active-directory/domain-join-error-0x534-no-mapping-between-account-names-and-security-ids-was-done.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,12 @@ When you try to join a computer to a domain, you receive the following error mes
2323
You review the *netsetup.log* log and found error messages that resemble the following:
2424

2525
```output
26-
mm/dd/yyyy hh:mm:ss:ms NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x534
27-
mm/dd/yyyy hh:mm:ss:ms NetpProvisionComputerAccount: LDAP creation failed: 0x534
28-
mm/dd/yyyy hh:mm:ss:ms ldap_unbind status: 0x0
29-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: Function exits with status of: 0x534
30-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: status of disconnecting from '\\<DC name>': 0x0
31-
mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x534
26+
NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x534
27+
NetpProvisionComputerAccount: LDAP creation failed: 0x534
28+
ldap_unbind status: 0x0
29+
NetpJoinDomainOnDs: Function exits with status of: 0x534
30+
NetpJoinDomainOnDs: status of disconnecting from '\\<DC name>': 0x0
31+
NetpDoDomainJoin: status: 0x534
3232
```
3333

3434
### Error detail

‎support/windows-server/active-directory/domain-join-error-0x6d9-there-are-no-more-endpoints-available-from-the-endpoint-mapper.md‎

Lines changed: 29 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -23,26 +23,26 @@ When you try to join a computer to a domain, you receive the following error mes
2323
You review the *netsetup.log* log and found error messages that resemble the following:
2424

2525
```output
26-
mm/dd/yyyy hh:mm:ss:ms NetpGetDnsHostName: Read NV Hostname: <hostname>
27-
mm/dd/yyyy hh:mm:ss:ms NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: <DNS domain>.<TLD>
28-
mm/dd/yyyy hh:mm:ss:ms NetpLsaOpenSecret: status: 0xc0000034
29-
mm/dd/yyyy hh:mm:ss:ms NetpGetLsaPrimaryDomain: status: 0x0
30-
mm/dd/yyyy hh:mm:ss:ms NetpLsaOpenSecret: status: 0xc0000034
31-
mm/dd/yyyy hh:mm:ss:ms NetpManageMachineAccountWithSid: NetUserAdd on \\<hostname>.<domain> for <computername>$ failed: 0x8b0
32-
mm/dd/yyyy hh:mm:ss:ms NetpManageMachineAccountWithSid: status of attempting to set password on \\<DC name>.<domain>.<tld> for <hostname>$: 0x0
33-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: status of creating account: 0x0
34-
mm/dd/yyyy hh:mm:ss:ms NetpGetComputerObjectDn: Unable to bind to DS on \\<DC name>.<domain>.<tld>: 0x6d9
35-
mm/dd/yyyy hh:mm:ss:ms NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn failed: 0x6d9
36-
mm/dd/yyyy hh:mm:ss:ms ldap_unbind status: 0x0
37-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: status of setting DnsHostName and SPN: 0x6d9
38-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: initiaing a rollback due to earlier errors
39-
mm/dd/yyyy hh:mm:ss:ms NetpGetLsaPrimaryDomain: status: 0x0
40-
mm/dd/yyyy hh:mm:ss:ms NetpManageMachineAccountWithSid: status of disabling account <hostname>$ on \\<DC name>.<domain>.<tld>: 0x0
41-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: rollback: status of deleting computer account: 0x0
42-
mm/dd/yyyy hh:mm:ss:ms NetpLsaOpenSecret: status: 0x0
43-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: rollback: status of deleting secret: 0x0
44-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomain: status of disconnecting from \\<DC name>.<domain>.<tld>: 0x0
45-
mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x6d9
26+
NetpGetDnsHostName: Read NV Hostname: <hostname>
27+
NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: <DNS domain>.<TLD>
28+
NetpLsaOpenSecret: status: 0xc0000034
29+
NetpGetLsaPrimaryDomain: status: 0x0
30+
NetpLsaOpenSecret: status: 0xc0000034
31+
NetpManageMachineAccountWithSid: NetUserAdd on \\<hostname>.<domain> for <computername>$ failed: 0x8b0
32+
NetpManageMachineAccountWithSid: status of attempting to set password on \\<DC name>.<domain>.<tld> for <hostname>$: 0x0
33+
NetpJoinDomain: status of creating account: 0x0
34+
NetpGetComputerObjectDn: Unable to bind to DS on \\<DC name>.<domain>.<tld>: 0x6d9
35+
NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn failed: 0x6d9
36+
ldap_unbind status: 0x0
37+
NetpJoinDomain: status of setting DnsHostName and SPN: 0x6d9
38+
NetpJoinDomain: initiaing a rollback due to earlier errors
39+
NetpGetLsaPrimaryDomain: status: 0x0
40+
NetpManageMachineAccountWithSid: status of disabling account <hostname>$ on \\<DC name>.<domain>.<tld>: 0x0
41+
NetpJoinDomain: rollback: status of deleting computer account: 0x0
42+
NetpLsaOpenSecret: status: 0x0
43+
NetpJoinDomain: rollback: status of deleting secret: 0x0
44+
NetpJoinDomain: status of disconnecting from \\<DC name>.<domain>.<tld>: 0x0
45+
NetpDoDomainJoin: status: 0x6d9
4646
```
4747

4848
### Error detail
@@ -53,25 +53,23 @@ mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x6d9
5353

5454
## Cause
5555

56-
Error 0x6D9 is logged when network connectivity is blocked between the joining client and the helper DC. The network connectivity services the domain join operation over port 135 or a port in the ephemeral range between 1025 to 5000 or 49152 to 65535. For more information, see [Service overview and network port requirements for Windows](../networking/service-overview-and-network-port-requirements.md).
56+
Error 0x6D9 is logged when network connectivity is blocked between the joining client and the Domain Controller (DC). The network connectivity services the domain join operation over port 135 or a port in the ephemeral range between 1025 to 5000 or 49152 to 65535. For more information, see [Service overview and network port requirements for Windows](../networking/service-overview-and-network-port-requirements.md).
5757

58-
The network connectivity issue can be caused by several factors, including Symantec Endpoint Protection (if it is installed on the helper DC), port exhaustion, and other potential issues.
58+
The network connectivity issue can be caused by several factors, including advanced security solutions with host firewalls installed on the DC, port exhaustion, and other potential issues.
5959

6060
## Resolution
6161

62-
1. On the joining client, open the *%systemroot%\\debug\\NETSETUP.LOG* file and determine the name of the helper DC selected by the joining client to perform the join operation. For example: the following NETSETUP.LOG sample shows that the joining client "APP_SRV" is using helper DC "DC1.CONTOSO.COM ":
62+
1. On the joining client, open the *%systemroot%\\debug\\NETSETUP.LOG* file and determine the name of the DC selected by the joining client to perform the join operation. For example: the following NETSETUP.LOG sample shows that the joining client "APP_SRV" is using DC "DC1.CONTOSO.COM ":
6363

6464
```output
65-
mm/dd hh:mm:ss NetpManageMachineAccountWithSid: NetUserAdd on '\\DC1.CONTOSO.COM' for 'APP_SRV$' failed: 0x8b0
66-
mm/dd hh:mm:ss NetpManageMachineAccountWithSid: status of attempting to set password on '\\DC1.CONTOSO.COM' for '<APP_SRV>$': 0x0
67-
mm/dd hh:mm:ss NetpJoinDomain: status of creating account: 0x0
68-
mm/dd hh:mm:ss NetpGetComputerObjectDn: Unable to bind to DS on '\\DC1.CONTOSO.COM': 0x6d9
65+
NetpManageMachineAccountWithSid: NetUserAdd on '\\DC1.CONTOSO.COM' for 'APP_SRV$' failed: 0x8b0
66+
NetpManageMachineAccountWithSid: status of attempting to set password on '\\DC1.CONTOSO.COM' for '<APP_SRV>$': 0x0
67+
NetpJoinDomain: status of creating account: 0x0
68+
NetpGetComputerObjectDn: Unable to bind to DS on '\\DC1.CONTOSO.COM': 0x6d9
6969
```
7070

71-
2. Verify that the joining client has network connectivity to the DC over the required ports and protocols used by the applicable operating system (OS) versions. Domain join clients connect a helper DC over Transmission Control Protocol (TCP) port 135 by the dynamically assigned port in the range between 49152 and 65535.
71+
2. Verify that the joining client has network connectivity to the DC over the required ports and protocols used by the applicable operating system (OS) versions. Domain join clients connect a DC over Transmission Control Protocol (TCP) port 135 by the dynamically assigned port in the range between 49152 and 65535.
7272
3. Ensure that the OS, software and hardware routers, firewalls, and switches allow connectivity over the required ports and protocols.
7373
4. Ensure that there are enough available ports for the operation. You can use tools like netstat to check for port availability and usage.
74-
5. If Symantec Endpoint Protection is installed on the helper DC, review its settings to ensure it isn't blocking the required ports.
74+
5. If advanced security solutions with host firewalls is installed on the DC, review its settings to ensure it isn't blocking the required ports.
7575
6. Consider other potential causes and troubleshoot accordingly. For example, check firewall rules, ensure proper DNS resolution, and verify the health of the DC.
76-
77-
[!INCLUDE [Third-party disclaimer](../../includes/third-party-disclaimer.md)]

0 commit comments

Comments
 (0)