What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

MS Netlogon Patch breaks PRTG sensors



Once we applied these patches, the stability of our PRTG instance was lost - the additional load involved with handling the more secure encryption must have pushed our probes over the limit and we're getting a lot of complaints now about the probe being overloaded and WMI sensors and such taking too long. Nothing in PRTG was changed, only this patch was applied to our DCs.

Have others seen this and reported it already? Is there a better option for addressing this in PRTG other than creating additional probes? I'm looking for guidance on best practice from PRTG.

This article details the related patch and changes to domain authentication once applied: https://support.microsoft.com/en-us/help/4557222/how-to-manage-the-changes-in-netlogon-secure-channel-connections-assoc

netlogon patch prtg

Created on Sep 22, 2020 5:11:40 PM

1 Reply



Hello Matt,

Thank you for your post.

We did not have any prior cases regarding this, so we do not have any information at the moment. However we will take a closer look at this.

In the mean time I would suggest to check if you are bale to make exceptions for server that need to comunicate with non-secure RPC.

Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Sep 23, 2020 11:08:42 AM by  Sasa Ignjatovic [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.