I'm trying to configure Auto-Discovery to use AD integration (filtered by OU) but receive the following error:

Error (Bad Request) The validation of at least one of the new objects failed because of the following: Active Directory cannot be accessed for "IP Selection" (Auto discovery setting)

The discovery works fine if I leave the OU field empty. I'm trying to use:

OU=Servers,OU=Infra,DC=removed,DC=removed,DC=removed,DC=removed (this is the distinguisedName field in AD)

The full error given is:

Version: 16.4.27.6720 Server: <removed> URL: addgroup2.htm?id=1&name_=Group+1&tags_=&discoverytype_=1&devicetemplate_=1&devicetemplate_=1&discoveryschedule_=0&ipselectmethod_=5&ipbase_=&iprangebegin_=1&iprangeend_=254&iplist_=&ipsubnet_=&ipoctetrange_=&iplistv6_=&ipou_=OU=Servers,OU=Infra,DC=....,DC=....,DC=..,DC=..&usedns_=1&skipknownips_=1&windowsconnection=0&windowsconnection=1&windowslogindomain_=&windowsloginusername_=&windowsloginpassword_=&linuxconnection=0&linuxconnection=1&linuxloginusername_=&linuxloginmode_=0&linuxloginpassword_=&privatekey_=&wbemprotocol_=https&wbemportmode_=0&wbemport_=5989&sshport_=22&sshelevatedrights_=1&elevationnamesudo_=&elevationnamesu_=&elevationpass_=&sshversion_devicegroup_=2&vmwareconnection=0&vmwareconnection=1&esxuser_=&esxpassword_=&esxprotocol_=0&vmwaresessionpool_=1&dbcredentials=0&dbcredentials=1&usedbcustomport_=0&dbport_=&dbauth_=0&dbuser_=&dbpassword_=&dbtimeout_=60&cloudcredentials=0&cloudcredentials=1&awsak_=&awssk_=&snmpversiongroup=0&snmpversiongroup=1&snmpversion_=V2&snmpcommv1_=public&snmpcommv2_=public&snmpauthmode_=authpHMACMD596&snmpuser_=&snmpauthpass_=&snmpencmode_=DESPrivProtocol&snmpencpass_=&snmpcontext_=&snmpport_=161&snmptimeout_=5&httpproxy=0&httpproxy=1&proxy_=&proxyport_=8080&proxyuser_=&proxypassword_=&accessgroup=0&accessgroup=1&accessrights_=1&accessrights_=1&accessrights_2614=-1&accessrights_2976=-1&accessrights_2533=-1&accessrights_2419=-1&accessrights_2416=-1&accessrights_2493=-1&accessrights_3492=-1&accessrights_201=-1&accessrights_2412=-1

Anyone know how to get past this?

Article Comments

The correct one would be: Servers,OU=Infra,DC=removed,DC=removed,DC=removed,DC=removed

The OU for the first OU has to be removed, PRTG will find it automatically then. If it doesn't work as well, please also omit all DC items from the string (i.e. only Servers,OU=Infra).


Nov, 2016 - Permalink

Worked a treat, thanks.


Nov, 2016 - Permalink

I don't know if it's OK for me to addon to this with the same problem...

We have a situation where the core server is in one domain (contoso.com) and I'm trying to setup a remote probe in another domain (fabrikam.com). However, auto-discovery doesn't work when I specify the OU, using the above syntax. I get the error: •Active Directory cannot be accessed for "IP Selection" (Auto discovery setting)

I've tried both: A,DC=fabrikam,DC=com and A

I have credentials set for Windows Systems in the Remote Probe settings, using my own admin account for testing, which has domain admin rights for fabrikam.com

Is this scenario perhaps not supported by PRTG?


Jan, 2017 - Permalink

I'll talk with the developer and let you know what he said :)


Jan, 2017 - Permalink

Could you try 

A,DC=fabrikam

...without DC=COM at the end?


Jan, 2017 - Permalink

Same error without DC=com at the end. =(


Jan, 2017 - Permalink

Hm. How about A,DC=fabrikam.com?


Jan, 2017 - Permalink

A,DC=fabrikam.com also does not work. Same error. =(


Jan, 2017 - Permalink

Is your PRTG webinterface available from outside of your network?
Feel free to post the credentials,I won't publish it. Then I can check it out :)


Jan, 2017 - Permalink

Our security policies don't permit sharing passwords. Can we setup a screen sharing session perhaps?


Jan, 2017 - Permalink

Sure. Please open up a ticket with support@paessler.com and state your time zone + the times when your available within the same :)


Jan, 2017 - Permalink