Re: Bug? Nessus can't parse it's own generated .nbe file??

Michel Arboi wrote:

> On Thu Apr 28 2005 at 19:33, Jason Haar wrote:
>
>  
>
> > I've been having real difficulty getting nessus to scan a DMZ in which
> > some HTTPS web servers aren't pingable - Nessus has been skipping them
> > (host is dead).
> >    
>
> Enable "TCP ping" option (it is by default) and make sure that 443 is
> in the port list (it is in "built-in" and "extended")
> Unless your server is not on port 443, of course.
>
>  
That isn't what I've found (see previous post: "why is this host being 
reported as dead?"

I've found that "built-in" scans 49 ports - not including 443.

I have never heard of "extended" before - the Nessus GUI popup makes no 
mention of it? I assume that contains more ports and was probably really 
what I wanted all along - thanks for that!

> Might be a bug in the text conversion. Did you try another format?
> HTML? Did you read the NBE with the GUI?
>
>  

Hopefully you got my followup where I accept all blame - yes it was a 
"bad" nbe file after all. :-}

Thanks for the "extended" tip!

--
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus