Since we migrated to 5.1.xx ip scanning is very slow to scan the defined network. Lansweeper is not able to scan all ip ranges within 24 hours.
Queue to be scanned ip addresses grow from day to day.
Also when we enable the IP scanning, lansweeper service is taking all available memory. That has the effect that the whole server performance goes down.
In 5.0.xx we did not recognize this issue.
EDIT:
I found the issue. Typing Error in one IP Rage. 10.x.x.x to 13.x.x.x. is an little bit heavy 😉
I'm surprised that the 5.0 version did it without issues. Maybe it is an option to prevent the Admin to define to big neetwork ranges.....
Cheers.
