Re: Varying results from scans

Josh Zlatin-Amishav wrote:
> On Mon, 20 Feb 2006, Ameet Zaveri wrote:
> > How do I go about debugging this situation? In looking at the
> > message log on the server side I noticed the following. It said
> > "Not launching openssl_denial.nasl against xx.xx.xx.197 none of
> > the required tcp ports are open (this is not an error)" for the
> > host where it did not find the hole. But it said "launching
> > openssl_denial.nasl against xx.xx.xx.198 [1060]" for the similar
> > host where it found the hole.
>
> Which port scanner[s] are you using?

And are you behind a firewall, that might start dropping packages while 
you are portscanning? That way you sometimes get results of a open port 
and other times you don't.

I know firewalls like in Cisco IOS based routers get aggressive and 
start dropping packages, if there are more than xxxx packages / second 
from a given host. Maybe that's the case here?

--

  Jesper S. Jensen
Basisnet og Sikkerhed
Uni-C - Århus, Danmark
   +45 8937-6666
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus