Merge pull request #10150 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-08 02:00 UTC

Author: learn-build-service-prod[bot]

support/windows-server/active-directory/restrict-ad-rpc-traffic-to-specific-port.md

@@ -62,9 +62,9 @@ Restart the computer for the new setting to become effective.
 Restart the Netlogon service for the new setting to become effective.
 
 > [!NOTE]
-> When you use the `DCTcpipPort` registry entry, and you set it to the same port as the `TCP/IP Port` registry entry, you receive Netlogon error event 5809 under `NTDS\Parameters`. This indicates that the port configured is in use, and you should choose a different port.
+> When you use the `DCTcpipPort` registry entry, and you set it to the same port as the `TCP/IP Port` registry entry, Netlogon error event 5809 is logged in the system log. This error indicates that the configured port is in use, and you should choose a different port.
 
-You'll receive the same event when you have a unique port, and you restart the Netlogon service on the domain controller. This behavior is by design. It occurs because of the way the RPC runtime manages its server ports. The port will be used after the restart, and the event can be ignored.
+You'll receive the same event when you have a unique port, and you restart the Netlogon service on the domain controller. This behavior is by design. It occurs because of the way the RPC runtime manages its server ports. The port will be used after the restart, and the event can be safely ignored.
 
 Administrators should confirm that the communication over the specified port is enabled if any intermediate network devices or software is used to filter packets between the domain controllers.