Scannig Target 'No credentials for this Domain' after SQL database migration

[KayP1992]

Hello,

I hope you could help me with the following problem.

Yesterday I migrated the SQL Lansweeper database from an old management system to a new one.
I used the given Lansweeper documentations.
I installed on the new Server a SQL Server 2017 Express and the Lansweeper (version 7.1.100.16)
The migration worked perfect.

Today I saw in the Scanning Targets that the 'Active Directory Computer Path' and 'Active Directory User Path' won´t get scanned.

I added the Scanning targets manual.
I couldn´t find a situation like this on Google and I hope you could help me.

ERROR:
Active Directory Computer Path: No potentially correct credentials
Active Directory User Path: No credentials for this Domain




Thank you in advance.

KayP

[tosch]

Hi,

you can find the Preferred Domain Controller settings under Scanning\Scanning Targets.
Select your Scannserver.

regards

Thomas

[RobDz]

Thanks for that - I don't have it configured, even adding it after the fact didn't resolve the issue either  

[julianbr]

I have the same issue with Lansweeper version 10.3.0.0 

I have not migrated to any new SQL databases, it just suddenly happened. It worked just fine earlier. 

[RobDz]

I'm just encountering this issue this week, same as you - even after upgrading to 10.3.1 .. the suggestions below, I'm having issues locating them (where is "preferred DC"), was your issue ever resolved?

[adm_kr]

Hello,

I have the same problem.
Do you found a solution for that?

- I set Windows credentials and mapped it to "Workgroup or Domain".
- I checked everything multiple times.
- LDAP checks are green.
- Preferred DC is set.

What ever I do, I will get this error:
Active Directory Domain - No credentials for this domain 
Active Directory Computer Path - No credentials for this domain
Active Directory User Path - No credentials for this domain

Best regards

[tosch · Accepted solution]

Hi,
i have the same problem.
But have it solved now by removing Preffered DC from all scanservers.

Maybe this will help you too.
Best regards

Thomas

[Lennart]

Thanks, it fixed my problem also, we got the problem yesterday, but removing Preferred Domain Controllers made it working again.

[adm_kr]

Wow, thank your very much. Works now.

Best regards

[julianbr]

This fixed the problem for me. Thanks!