Scanning Queue Timeout Adjustment

[aeoncs]

Hi, I have a question, I can't seem to find anything on the forums here about it. 

At the moment when scanning devices on our network if the device is offline Lansweeper will try to continue scanning it for 1 hour before moving on to the next.. As we can our client machines as well as servers, we often run into all threads being clogged with offline machines causing huge delays.

So is it possible to reduce this 1 hour retry time to around 30 seconds? 

[DavidPK]

Hi ,

There are some settings under the IP range targets you can check that could have an impact on what you are experiencing. 

1. Ping Time-out: This setting determines how long Lansweeper will wait before moving on the next device after considering the asset unreachable.
2. Don't Ping, if enabled Lansweeper will try every IP address in a range even it cannot be pinged. 

There are more settings listed in the following KB article that can be checked also to ensure the system is optimized 

https://community.lansweeper.com/t5/scanning-your-network/scanning-with-an-ip-range-scanning-target/...

[aeoncs]

Hi, thanks for the reply, Don't Ping needs to be selected when sweeping the client machine vlans, as they can pick up a different IP. Ping Timeout is set to 2 seconds, I believe this is the default.

However, I am talking about known devices that have been previously scanned and already exist in Lansweeper, not the IP Scanning queue, but the Windows Computer Scanning queue.  When a scan is attempted on one of those and it is powered off, Lansweeper seems to retry for an hour before giving up and moving on to the next device. This is causing some pretty big delays in scanning as we have close to 5000 machines that need to be scanned in the client vlans. 

[DavidPK]

Hello there! 

Please submit a support request so we can troubleshoot this issue. We'll need more details and system logs

How to contact support?

Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away. 

Using the GatherLogs tool.