Updates from editor

Author: v-phoebh

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

@@ -1,7 +1,7 @@
 ---
-title: Domain join error 0x40 "The specified network name is no longer available"
-description: Addresses the error "The specified network name is no longer available" encountered during domain join operations.
-ms.date: 03/26/2025
+title: Error 0x40 The Specified Network Name Is No Longer Available
+description: Addresses the error The specified network name is no longer available encountered during domain join operations.
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -16,11 +16,11 @@ This article addresses the error code 0x40 encountered during domain join operat
 
 ## Symptoms
 
-The following error messages occur when you try to join the computer to the domain:
+When you try to join a computer to a domain, you receive the following error message:
 
-> The specified network name is no longer available
+> The specified network name is no longer available.
 
-You review the *netsetup.log* log and found error messages that resemble the following:
+When you review the **netsetup.log** file, you find error messages that resemble the following entries:
 
 ```output
 NetUseAdd to \\<dc_fqdn>\IPC$ returned 64
@@ -33,13 +33,13 @@ NetpDoDomainJoin: status: 0x40
 
 ### Error detail
 
-|HEX error|Decimal error|Symbolic Error String|Friendly Error|
+|Hexadecimal error|Decimal error|Symbolic error string|Friendly error|
 |---|---|---|---|
 |0x40|64|ERROR_NETNAME_DELETED|The specified network name is no longer available.|
 
 ## Cause
 
-This error is logged when the client computer lacks network connectivity on TCP port 88 between the client and the Domain Controller (DC), which is used for Key Distribution Center (KDC) request packet. For example, the error could be caused if some firewall device between the client and the DC.
+This error is logged when the client computer lacks network connectivity on Transmission Control Protocol (TCP) port 88 between the client and the domain controller (DC), which is used for the Key Distribution Center (KDC) request packet. For example, the error might be caused by some firewall device between the client and the DC.
 
 ## Troubleshoot
 
@@ -51,7 +51,7 @@ To troubleshoot this issue, you can run the following command to test the connec
 Test-NetConnection <IP_address_of_the_DC> -Port 88
 ```
 
-Expected Output:
+Expected output:
 
 ```output
 ComputerName           : <ip_address>
@@ -63,18 +63,18 @@ PingReplyDetails (RTT) : 0 ms
 TcpTestSucceeded       : False
 ```
 
-The output indicates that the Kerberos Port TCP 88 is not open between the client and the DC.
+The output indicates that the Kerberos port TCP 88 isn't open between the client and the DC.
 
 ### Network trace
 
 The issue is related to Server Message Block (SMB).
 
 1. Use the `net use` command to access the same Universal Naming Convention (UNC) path and reproduce the issue.
-2. Collect a network trace of the "net use" command execution.
+2. Collect a network trace of the `net use` command execution.
 
 #### Example
 
-The following is an example of a network trace:
+Here's an example of a network trace:
 
 ```output
 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}
@@ -103,4 +103,4 @@ DC1.ADATUM.COM         CLIENT1            TCP      TCP:Flags=...A...., SrcPort=K
 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 
 ```
 
-From the trace, we can find the 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.
+From the trace, you can find the 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 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

@@ -1,7 +1,7 @@
 ---
-title: Domain join error 0x534 "No mapping between account names and security IDs was done"
-description: Addresses the error "No mapping between account names and security IDs was done" encountered during domain join operations.
-ms.date: 03/26/2025
+title: Error 0x534 No Mapping Between a Account Names and Security IDs Was Done
+description: Addresses the error No mapping between account names and security IDs was done encountered during domain join operations.
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,13 +14,13 @@ ms.custom:
 
 This article addresses the error code 0x534 encountered during domain join operations.
 
-## Symptom
+## Symptoms
 
 When you try to join a computer to a domain, you receive the following error message:
 
 > No mapping between account names and security IDs was done.
 
-You review the *netsetup.log* log and found error messages that resemble the following:
+When you review the **netsetup.log** file, you find error messages that resemble the following entries:
 
 ```output
 NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x534
@@ -33,18 +33,18 @@ NetpDoDomainJoin: status: 0x534
 
 ### Error detail
 
-|HEX error|Decimal error|Symbolic Error String|
+|Hexadecimal error|Decimal error|Symbolic error string|
 |---|---|---|
 |0x534|1332|ERROR_NONE_MAPPED|
 
 ## Cause
 
-The domain-join graphical user interface (GUI) or user interface (UI) can call the NetJoinDomain API twice to join a computer to a domain. The first call is made without the "create" flag being specified to locate a pre-created computer account in the target domain. If no account is found, a second `NetJoinDomain` API call might be made with the "create" flag specified.
+The domain-join graphical user interface (GUI) or user interface (UI) can call the `NetJoinDomain` API twice to join a computer to a domain. The first call is made without specifying the "create" flag to locate a pre-created computer account in the target domain. If no account is found, a second `NetJoinDomain` API call might be made with the "create" flag specified.
 
-The 0x534 error code or status is commonly logged as a transient error when domain join searches the target domain or when the domain join UI is used and certain values are present in the options bit (values of 25, 27, 425, or 427 are common).
+The 0x534 error code or status is commonly logged as a transient error when a domain join searches for the target domain or when the domain join UI is used and certain values are present in the options bit (values of 25, 27, 425, or 427 are common).
 
-In another scenario, this error occurs when you try to change the password for a machine account. However, the account can't be found on the targeted Domain Controller (DC), likely because the account wasn't created or due to replication latency or a replication failure. Check the bit flags in the join options to see if the type of join being performed is relying on a pre-created or newly created computer account.
+In another scenario, this error occurs when you try to change the password for a machine account. However, the account can't be found on the targeted domain controller (DC), likely because the account wasn't created or due to replication latency or a replication failure.
 
 ## Resolution
 
-To fix the issue, focus on the bits in the options flag. Check whether the type of join being performed is relying on preexisting accounts or requires creating new ones.
+To fix the issue, focus on the bits in the options flag. Check whether the type of join being performed relies on preexisting accounts or requires creating new ones.

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

@@ -1,7 +1,7 @@
 ---
-title: Domain join error 0x6D9 "There are no more endpoints available from the endpoint mapper"
-description: Addresses the error "There are no more endpoints available from the endpoint mapper" encountered during domain join operations.
-ms.date: 03/26/2025
+title: Error 0x6D9 There Are No More Endpoints Available from the Endpoint Mapper
+description: Addresses the error There are no more endpoints available from the endpoint mapper encountered during domain join operations.
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -14,13 +14,13 @@ ms.custom:
 
 This article addresses the error code 0x6D9 encountered during domain join operations.
 
-## Symptom
+## Symptoms
 
 When you try to join a computer to a domain, you receive the following error message:
 
 > There are no more endpoints available from the endpoint mapper.
 
-You review the *netsetup.log* log and found error messages that resemble the following:
+When you review the **netsetup.log** file, you find error messages that resemble the following entries:
 
 ```output
 NetpGetDnsHostName: Read NV Hostname: <hostname>
@@ -47,19 +47,19 @@ NetpDoDomainJoin: status: 0x6d9
 
 ### Error detail
 
-| HEX error | Decimal error | Symbolic Error String | Friendly Error                                                  |
+| Hexadecimal error | Decimal error | Symbolic error string | Friendly error                                                  |
 | --------- | ------------- | --------------------- | --------------------------------------------------------------- |
 | 0x6d9     | 1753          | EPT_S_NOT_REGISTERED  | There are no more endpoints available from the endpoint mapper. |
 
 ## Cause
 
-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).  
+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).  
 
 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.
 
 ## Resolution
 
-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 ":
+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 the DC "DC1.CONTOSO.COM":
 
    ```output
    NetpManageMachineAccountWithSid: NetUserAdd on '\\DC1.CONTOSO.COM' for 'APP_SRV$' failed: 0x8b0
@@ -68,8 +68,8 @@ The network connectivity issue can be caused by several factors, including advan
    NetpGetComputerObjectDn: Unable to bind to DS on '\\DC1.CONTOSO.COM': 0x6d9
    ```
 
-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.
+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 to a DC over Transmission Control Protocol (TCP) port 135, which is a dynamically assigned port between 49152 and 65535.
 3. Ensure that the OS, software and hardware routers, firewalls, and switches allow connectivity over the required ports and protocols.
-4. Ensure that there are enough available ports for the operation. You can use tools like netstat to check for port availability and usage.
-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.
-6. Consider other potential causes and troubleshoot accordingly. For example, check firewall rules, ensure proper DNS resolution, and verify the health of the DC.
+4. Ensure that there are enough ports available for the operation. You can use tools like netstat to check for port availability and usage.
+5. If advanced security solutions with host firewalls are installed on the DC, review their settings to ensure they aren't blocking the required ports.
+6. Consider other potential causes and troubleshoot accordingly. For example, check firewall rules, ensure proper Domain Name System (DNS) resolution, and verify the health of the DC.

support/windows-server/active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain.md

@@ -1,7 +1,7 @@
 ---
 title: Failure When You Use an Existing Computer Account to Join a Domain
 description: Addresses the issue of failing to join a computer to a domain when an existing computer account with the same name already exists.
-ms.date: 03/27/2025
+ms.date: 03/28/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting

support/windows-server/toc.yml

@@ -357,11 +357,11 @@ items:
       href: ./active-directory/cannot-connect-internet-domain.md
     - name: Default limit to workstation numbers
       href: ./active-directory/default-workstation-numbers-join-domain.md
-    - name: 'Domain join error 0x534 "No mapping between account names and security IDs was done"'
+    - name: 'Error 0x534 "No mapping between account names and security IDs was done"'
       href: ./active-directory/domain-join-error-0x534-no-mapping-between-account-names-and-security-ids-was-done.md
-    - name: 'Domain join error 0x6D9 "There are no more endpoints available from the endpoint mapper"'
+    - name: 'Error 0x6D9 "No more endpoints available from the endpoint mapper"'
       href: ./active-directory/domain-join-error-0x6d9-there-are-no-more-endpoints-available-from-the-endpoint-mapper.md
-    - name: 'Domain join error 0x40 "The specified network name is no longer available"'
+    - name: 'Error 0x40 "The specified network name is no longer available"'
       href: ./active-directory/domain-join-error-0x40-the-specified-network-name-is-no-longer-available.md
     - name: Failure when you use an existing computer account to join a domain
       href: ./active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain.md