I'm testing PRTG with the hope of convincing my employer to buy it. One of the deal-breakers is monitoring AD replication errors.

When I try to add the Active Directory Repliation Errors sensor on a DC in a remote site I get an error saying "Timeout (5000 ms)". I have been able to add the same sensor to the Domain Controllers in the HQ Site (where I am located)

I have specified my own admin credentials (as a test) in the "Credentials for Windows System" section of the parent group.

Is there something else I need to configure?

Article Comments

Hello,

Additionally to valid Domain administrator credentials in the "Credentials for Windows System" section, the sensors requires the probe system to be part of the domain whose AD you monitor.


Dec, 2016 - Permalink

I'm having a similar issue in that adding the Active Directory Repliation Errors sensor on to my DCs in a far remote site returns the "Timeout (5000 ms)" error. I've got two DCs with high latent links between that I cannot add to. Is there a way to bump up the time-out?

Thanks, Randolfini


May, 2017 - Permalink

Hello Randy,

There is a registry available to increase this timeout, I will directly contact you with the required settings.

Best regards, Felix


May, 2017 - Permalink

Hi,

I'm trying to add the Active Directory Repliation Errors sensor on a DC, appears the error "Timeout (5000 ms)". In some servers of my infrastructure in PRTG if I can add this sensor without problem but in others no.

I check the "Credentials for Windows System" and the version .NET 4.5 installed in the servers and all It`s correct.

Could you help me to include this sensor?

Thanks.


Jun, 2017 - Permalink

Hi Ruben,

I also sent an email with the instructions to you.

Best regards, Felix


Jun, 2017 - Permalink

Can you also send me the instuctions? I have the same problem (Timeout 5000ms). Best regards, Markus


Jun, 2017 - Permalink

Sure!


Jun, 2017 - Permalink

Hi Felix Saure ,

can you send me the instructions please , or post it here thanks in advance

regards


Aug, 2017 - Permalink

I am experiencing the same issue. Can you please provide me the fix.

Thank you!


Sep, 2017 - Permalink

Hi, I am also having the timeout issue when adding the probe for AD replication. Would I be able to get the instructions on how to resolve this?


Dec, 2017 - Permalink

Hello gsansen,

I've sent you the details.

Kind regards,

Erhard


Dec, 2017 - Permalink

Hello Erhard,

can you send me the details as well please? Please use this email address jankular.ivan@gmail.com Thanks a lot!

Regards


Dec, 2017 - Permalink

Hi, I am also having the timeout issue when adding the probe for AD replication. Would I be able to get the instructions on how to resolve this? Regards


Jun, 2018 - Permalink

Hello Heitec,

On the probe system that runs this sensor (PRTG server or remote probe if applicable), you can raise the timeout period with a registry "hack":

  1. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor\Probe\
  2. Add DWORD: MetaScanTimeout
  3. Possible decimal value (in seconds): 1-2147483647
  4. Restart service "PRTG Probe" for the change to take effect.

Sometimes it's required to set a value like 30 or even 60 in order to get it to work.

Kind regards,

Erhard


Jun, 2018 - Permalink