
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 10:09 PM
Fixing Lansweeper Active Directory USER LDAP Syncing Error
In our organization we use lansweeper for ticketing and system inventory and management. Recently we had an issue where our AD users would not sync with lansweeper. The error shown was that the LDAP Server was unavailable

The issue was caused by using a preferred domain controller that had died. Theses settings are under "Scanning Targets"

We removed the Preferred domain controller

And setup a new scan

Setup a new scan after the preferred ad controller has been removed

Lansweeper Syncing with AD
After the scan the Users started to sync with the AD Controller again. However having had this issue once before, you may need to reboot the lansweeper server if the users continue to have the LDAP error after the rescan. After the reboot the LDAP Error should be gone.

You can find more posts on my blog https://optionkey.blogspot.ca
In our organization we use lansweeper for ticketing and system inventory and management. Recently we had an issue where our AD users would not sync with lansweeper. The error shown was that the LDAP Server was unavailable

The issue was caused by using a preferred domain controller that had died. Theses settings are under "Scanning Targets"

We removed the Preferred domain controller

And setup a new scan

Setup a new scan after the preferred ad controller has been removed

Lansweeper Syncing with AD
After the scan the Users started to sync with the AD Controller again. However having had this issue once before, you may need to reboot the lansweeper server if the users continue to have the LDAP error after the rescan. After the reboot the LDAP Error should be gone.

You can find more posts on my blog https://optionkey.blogspot.ca
Labels:
- Labels:
-
General Discussion
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-17-2018 05:57 PM
FYI for anyone having this issue:
This issue was fixed in version 6.0.230.45. Updating to a more recent version should also resolve the issue.
Fixed: #624402 Several issues with preferred domain controllers submitted under Scanning\Scanning Targets: changes not taking effect until a Lansweeper service restart, inability to submit multiple preferred DCs for the same domain across multiple scanning servers, use of preferred DCs preventing successful Active Directory User/Group Path scans
This issue was fixed in version 6.0.230.45. Updating to a more recent version should also resolve the issue.
