In my new Penetrator (SFF 32 concurrent IP) installation, I’ve noticed that scans for one specific server are taking much longer (5+ hours) compared to other installations in similar environments. All servers are in the same broadcast domain, with no firewalls or L3 devices between the scanner and server. I can't pinpoint the cause for the delay on this specific server. What can I do to diagnose the issue? What information can I provide to assist in troubleshooting, and how can I gather it?
There could be several factors causing the delay:
- Is the issue isolated to one specific IP, or are multiple IPs affected?
- Target System Restrictions: The server may be limiting or blocking connections from the Penetrator, slowing the scan.
- Number of Open Ports: A high number of open ports can significantly increase scan times.
- Monitor the Scan: While scanning, click the progress bar to view detailed information. Identifying which module takes longer could help pinpoint the issue.
- Database Size: Larger vulnerability databases may slow some checks.
Please monitor the scan and provide more information about any specific slow modules to help diagnose further.
Thanks!
Comments
0 comments
Please sign in to leave a comment.