I'm scanning an environment just now, where I am repeatedly hitting connectivity issues, that cause the scan to pause.
The error message is:
Connectivity issue, Reason: ServerConsecutive, Server:<ip address>:80, Error:(100) Unable to parse WebServer response: Unable to read data from the transport connection: A conection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
I've looked at the traffic log, and I can see large numbers of 'POST' messages, but I cannot see responses in the traffic monitor, so I assume after a specified number of 'no responses' the scan will halt.
I tried modifying some settings, to perhaps even get the scan to pause more quickly in this scenario (although this could be detrimental in that I may have made it more prone to stopping now, as less responses are needed to trigger this action). I modified:
Consecutive 'single host' retry failures to stop scan from 50 to 10
Consecutive 'any host' retry failures to stop scan from 150 to 15
Is there anything I can do to prevent the scan 'pausing', as obviously I want to complete the scan as quickly as possible?
Is there anything I can do to prevent the error in the first instance? Is this a software issue?
I've attached a depersonalized sample 'POST' message that got no response.