You've set up your IP range scanning target to scan your Windows devices. You have several Windows accounts, for different types of setups. You've mapped all these credentials to the IP range scanning target... You're all set to go!
But suddenly you're getting locked out accounts and errors such as:
- Too many logins on the same IP range
- Not using the most common credential as “Global credentials”
What happened?
When Lansweeper scans your network with the IP Range scanning target, it will iterate through the list of mapped credentials and will try to log in. If the login attempt fails, Lansweeper will take the next credential and try again. As a last resort it will try the global credentials.
So logically, depending on the number of credentials that are mapped to the IP Range scanning target, and the number of login attempts set for a given device, this can result in the account being locked out.
Now what?
You should limit the number of credentials used for scanning.
For example:
Set up only one account that has the required privileges to scan all your Windows assets, and set up another account that has privileges to scan your domain controllers. Set account for domain controllers as a global credential and map the other credential to the IP Range scanning target.
Was this post helpful? Leave a Kudo!
Did you have a similar issue and a different solution? Share your work in the comments below and help your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions or Community Forum.
If you can't find what you're looking for, create a post in our Community Forum.
