Skip to content

Natew na kb secure ssltls link fix #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from
Open

Natew na kb secure ssltls link fix #314

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8ddf548
Add PowerShell script written by Joe Dibley that removes Auditor UAVR…
nwx-natew Oct 23, 2025
555cb19
Merge pull request #303 from netwrix/dev
ndm-farhan Oct 29, 2025
fd1af7e
Fix links referencing KB article titled "Connection Issue when TLS 1.…
nwx-natew Oct 29, 2025
6b1c67e
Merge branch 'netwrix:main' into natew-na-kb-secure-ssltls-link-fix
nwx-natew Oct 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions ...uld_not_create_ssltls_secure_channel_error_in_windows_server_monitoring_plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,6 @@ knowledge_article_id: kA04u000000wnpYCAQ
products:
- auditor
---

# Could Not Create SSL/TLS Secure Channel Error in Windows Server Monitoring Plan

## Symptoms
Expand All @@ -35,7 +34,7 @@ products:

## Resolutions

- Enable TLS 1.2 in your environment − refer to the following article for additional information: Connection Issue when TLS 1.2 Is Required.
- Enable TLS 1.2 in your environment − refer to the following article for additional information: [Connection Issue when TLS 1.2 Is Required.](/docs/kb/auditor/сonnection_issue_when_tls_1.2_is_required.md)
- In case TLS protocol versions are limited to specific versions in your environment, make sure to allow the operating system to select the protocol for incoming and outgoing communication. Refer to the following article for additional information: [Client and Server Cannot Communicate, Because They Do Not Possess a Common Algorithm](/docs/kb/auditor/client-and-server-cannot-communicate-because-they-do-not-possess-a-common-algorithm.md).
- Review the certificate used for Windows Server auditing:
1. In the Netwrix Auditor server, either press **Win + R** or launch the **Run** command window.
Expand All @@ -44,12 +43,12 @@ products:
4. In the left **Available snap-ins** window, select **Certificates**, and click **Add >**.

> **NOTE:** Once you add the **Certificates** snap-in, the following options should be selected in the prompted pop-up windows: **Computer account** > **Local computer** > **Finish** > **OK**.

>
5. In the left pane, expand the **Certificates (Local Computer)** store, and proceed to **Netwrix Auditor for Windows Server** > **Certificates**.
6. Review the certificate located in the **Certificates** folder. If expired (or multiple certificates are present), right-click the corresponding certificate and select **Delete**.
7. Restart the server to reissue the certificate.

## Related Articles

- Connection Issue when TLS 1.2 Is Required
- [Client and Server Cannot Communicate, Because They Do Not Possess a Common Algorithm](/docs/kb/auditor/client-and-server-cannot-communicate-because-they-do-not-possess-a-common-algorithm.md)
- [Connection Issue when TLS 1.2 Is Required](/docs/kb/auditor/сonnection_issue_when_tls_1.2_is_required.md)
- [Client and Server Cannot Communicate, Because They Do Not Possess a Common Algorithm](/docs/kb/auditor/client-and-server-cannot-communicate-because-they-do-not-possess-a-common-algorithm.md)
Loading