From c85bed908acafc5f13038027266a229bfd6907bc Mon Sep 17 00:00:00 2001 From: Hil-Ram-NWX Date: Wed, 12 Nov 2025 13:32:38 -0500 Subject: [PATCH] Update section title from 'Related Articles' to 'Related Links' Using this as a test for forked PRs --- ...t-failed-because-connected-party-did-not-properly-respond.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/kb/accessanalyzer/error-connection-attempt-failed-because-connected-party-did-not-properly-respond.md b/docs/kb/accessanalyzer/error-connection-attempt-failed-because-connected-party-did-not-properly-respond.md index 92c16ab7a6..30345c5e05 100644 --- a/docs/kb/accessanalyzer/error-connection-attempt-failed-because-connected-party-did-not-properly-respond.md +++ b/docs/kb/accessanalyzer/error-connection-attempt-failed-because-connected-party-did-not-properly-respond.md @@ -58,7 +58,7 @@ Test-NetConnection -ComputerName $RPC_host -Port 8767 -InformationLevel Detailed - If the proxy is not installed, then ensure it is installed and running following these steps: Netwrix Access Analyzer v12.0 > **File System Proxy Service Installation**. - If the proxy is installed and running, then the environment must either have a firewall or other security software preventing communication on ports `8767` and `8766`. -## Related Articles +## Related Links For more information on port requirements, please see the various guides for each scan mode below: