Ping Failures

If the Scan Engine is unable to ping a previously unscanned target, it will not attempt to scan it, as it regards it as being unreachable.

This may be because of a network/firewall issue, or it may be because the target is offline.

Ping failure (per project)

Given a ProjectID, to find which targets could not be scanned as they were unreachable, the following query can be used.

SELECT jobProj.ProjectID
     , ch.Target
     , ch.Label
	 , ch.DurationMilliseconds
	 , ch.Connection
	 , ch.message
	 , ch.AttemptDate
FROM history.t_CommandHistory ch 
    INNER JOIN jobs.t_JobLocationProjectIPRange AS jobProj ON jobProj.JobID = ch.JobID
WHERE ProtocolId=5 
  AND message LIKE '%Failed%' 
-- === Change this line ==== --
   AND jobProj.ProjectID = 1
-- ========================= --
ORDER BY AttemptDate DESC

Ping success

If you want to see the results of successful pings (for example to look at how long it took to complete - longer times imply connections that are slower or having higher latency) then add the word NOT in the WHERE clause

Successful pings

SELECT jobProj.ProjectID
     , ch.Target
     , ch.Label
     , ch.DurationMilliseconds
     , ch.Connection
     , ch.message
     , ch.AttemptDate
FROM history.t_CommandHistory ch
    INNER JOIN jobs.t_JobLocationProjectIPRange AS jobProj ON jobProj.JobID = ch.JobID
WHERE ProtocolId=5
  AND message NOT LIKE '%Failed%'
-- === Change this line ==== --
   AND jobProj.ProjectID = 1
-- ========================= --
ORDER BY AttemptDate DESC