I've posted previously but haven't received a clear answer on this.
When setting up automated subnet scans, if a scan over runs, and causes a queue of scans to build up behind it, the application will not complete the first scan. I re-worked our scanning schedule to try and limit the cross over of scans. But when you're trying to scan a large number of subents, this isn't easy.
I've reduced the impact with the re-work of the scan schedule. But it's still an issue.
Are there any other potential fixes for this problem? Is there a general maximum number of scans that should be queued at any one time? I don't think there is more than 3 or 4 at any time.
