Skip to content

Commit b3e09dc

Browse files
authored
Merge pull request #8781 from Deland-Han/main
remove duplications.
2 parents acc8127 + cae0b9d commit b3e09dc

1 file changed

Lines changed: 1 addition & 39 deletions

File tree

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
@@ -87,45 +87,7 @@ For more information, see [Error code 0xa8b: An attempt to resolve the DNS name
8787

8888
### Error code 0x40
8989

90-
The following error messages occur when you try to join the computer to the domain:
91-
92-
> The specified network name is no longer available
93-
94-
:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/domain-join-error-message.png" alt-text="Screenshot of the dialog box showing the error message for error code 0x40.":::
95-
96-
Here's an example from the *netsetup.log* file:
97-
98-
```output
99-
mm/dd/yyyy hh:mm:ss:ms NetpValidateName: checking to see if '<domain_name>' is valid as type 3 name
100-
mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid [ Exists ] for '<domain_name>' returned 0x0
101-
mm/dd/yyyy hh:mm:ss:ms NetpValidateName: name '<domain_name>' is valid for type 3
102-
mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: trying to find DC in domain '<domain_name>', flags: 0x40001010
103-
mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: failed to find a DC having account 'CLIENT1$': 0x525, last error is 0x0
104-
mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: status of verifying DNS A record name resolution for 'DCA.<domain_name>': 0x0
105-
mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: found DC '\\<dc_fqdn>' in the specified domain
106-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
107-
mm/dd/yyyy hh:mm:ss:ms NetpDisableIDNEncoding: using FQDN <domain_name> from dcinfo
108-
mm/dd/yyyy hh:mm:ss:ms NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on '<domain_name>' succeeded
109-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
110-
mm/dd/yyyy hh:mm:ss:ms NetUseAdd to \\<dc_fqdn>\IPC$ returned 64
111-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: status of connecting to dc '\\<dc_fqdn>': 0x40
112-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: Function exits with status of: 0x40
113-
mm/dd/yyyy hh:mm:ss:ms NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on '<domain_name>' returned 0x0
114-
mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpResetIDNEncoding on '<domain_name>': 0x0
115-
mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x40
116-
```
117-
118-
This error is logged when the client computer lacks network connectivity on TCP port 88 between the client machine and the DC. To troubleshoot this issue, you can run the following command to test the connection:
119-
120-
```PowerShell
121-
Test-NetConnection <IP_address_of_the_DC> -Port 88
122-
```
123-
124-
Expected Output:
125-
126-
:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/test-netconnection-output-88.png" alt-text="Screenshot that shows the Test-NetConnection command for TCP port 88 output.":::
127-
128-
The output indicates that the Kerberos Port TCP 88 is open between the client and the DC.
90+
For more information, see [Domain join error 0x40 "The specified network name is no longer available"](domain-join-error-0x40-the-specified-network-name-is-no-longer-available.md).
12991

13092
### Error code 0x54b
13193

0 commit comments

Comments
 (0)