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

LDAP sensor - every 2nd check is slow

Votes:

0

I have 3 x 2008R2 domain controllers at 2008R2 functional level. The checks in PRTG are alternating between 2200ms and 5ms. I have copied some of the output below. I updated to the latest version to see if it would make a difference.

If I use the powershell script from here it is consistent with about 5ms. https://rcmtech.wordpress.com/2014/10/07/powershell-ldap-response-time-monitor/

How can I get consistent results with PRTG?

11/01/2018 3:14:09 PM 5 msec 0 % 100 % 11/01/2018 3:13:41 PM 2,299 msec 0 % 100 % 11/01/2018 3:13:09 PM 6 msec 0 % 100 % 11/01/2018 3:12:41 PM 2,297 msec 0 % 100 % 11/01/2018 3:12:09 PM 5 msec 0 % 100 % 11/01/2018 3:11:41 PM 2,297 msec 0 % 100 % 11/01/2018 3:11:09 PM 9 msec 0 % 100 % 11/01/2018 3:10:41 PM 2,308 msec 0 % 100 % 11/01/2018 3:10:09 PM 5 msec 0 % 100 % 11/01/2018 3:09:41 PM 2,294 msec

active-directory ldap prtg15

Created on Jan 11, 2018 4:29:12 AM

Last change on Jan 11, 2018 2:36:17 PM by Erhard Mikulik [Paessler Support]



5 Replies

Votes:

0

Hello Aimee,

Did you confirm this with the script running on the same host as the responsibe PRTG server/remote probe that runs the sensor? If not, please run the test again on the responsible probe system.

Kind regards,

Erhard

Created on Jan 11, 2018 2:38:11 PM by Erhard Mikulik [Paessler Support]



Votes:

0

So, running the script on the same server as PRTG has the same issue of slow responses. Looks like I have some more investigation to do.

Thanks for the advice.

Created on Jan 12, 2018 1:09:21 AM



Votes:

0

Hi Aimee,

You're welcome. Maybe you can share then what you've found out.

Kind regards,

Erhard

Created on Jan 12, 2018 8:56:08 AM by Erhard Mikulik [Paessler Support]



Votes:

0

LDAP tests work fine on Windows 10, 2012, 2016, 2008. The issue only occurs on 2008R2.

Also, if I use the IP address instead of FQDN or netbios name, it works fine too. DNS response times are good in PRTG, so I don't think its our DNS server.

I think there is a Group policy or security policy causing this.

Created on Jan 15, 2018 10:54:17 PM



Votes:

0

Hi Aimee,

Thank you for sharing your findings you had so far!

Kind regards,

Erhard

Created on Jan 16, 2018 9:12:54 AM by Erhard Mikulik [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.