
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2020 04:26 PM
Hi Team,
We are facing 'The LDAP server returned an unknown error' in server logs every 20 - 30 sec for user OU.
Can you please help to resolve the issue.
Regards,
Mangesh Dahitule
We are facing 'The LDAP server returned an unknown error' in server logs every 20 - 30 sec for user OU.
Can you please help to resolve the issue.
Regards,
Mangesh Dahitule
Labels:
- Labels:
-
General Discussion
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-22-2020 09:55 AM
To provide you with some context, both the active domain scanning target and user scanning target will query the LastLogon attribute, and try to connect to all domain controllers to get the highest value for this attribute.
It is "expected" behaviour that Lansweeper will not be able to access all DCs, and as such the error messages in the server log do not really serve a purpose, as there is no real issue. We have already escalated the issue to our development so that they can look into optimizing this page.
If required, you can disable the scanning of LastLogon for users in the Active Directory Scanning Options section under Configuration\Server Options.
It is "expected" behaviour that Lansweeper will not be able to access all DCs, and as such the error messages in the server log do not really serve a purpose, as there is no real issue. We have already escalated the issue to our development so that they can look into optimizing this page.
If required, you can disable the scanning of LastLogon for users in the Active Directory Scanning Options section under Configuration\Server Options.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2020 11:09 AM
MDahitule wrote:
To provide you with some context, both the active domain scanning target and user scanning target will query the LastLogon attribute, and try to connect to all domain controllers to get the highest value for this attribute.
It is "expected" behaviour that Lansweeper will not be able to access all DCs, and as such the error messages in the server log do not really serve a purpose, as there is no real issue. We have already escalated the issue to our development so that they can look into optimizing this page.
If required, you can disable the scanning of LastLogon for users in the Active Directory Scanning Options section under Configuration\Server Options.
I have disabled the scanning of lastlogon attribute but the problem remains. But my problem is different because it happens on the computers OU.
I have a domain controller in Azure that is not accessible by Lasweeper, but I have a local controller as my favorite.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2020 10:24 AM
Good to know we're not the only ones with the problem.
We got the problem with the last Update
Website Version: 8.0.130.14
LANSWEEPERSEVRER 8.0.130.14
I set a preferred DC and reboot the server but it doesn't help.
I also check the LDAP connection from the Lansweeper with an Test tool and the connection was successful.
Best,
Stefan
We got the problem with the last Update
Website Version: 8.0.130.14
LANSWEEPERSEVRER 8.0.130.14
I set a preferred DC and reboot the server but it doesn't help.
I also check the LDAP connection from the Lansweeper with an Test tool and the connection was successful.
Best,
Stefan
