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

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.

> In the end I had to turn off both tcp and icmp ping options

There must be an open TCP port somewhere, no? The "extended" port list
is slow but good on firewalled hosts, unless they use only uncommon
ports. 

> and configure it to use the nmap scanner option.

Do you use up to date plugins by the way? nmap.nasl now adds -P0. In
older versions, it was possible to enable nmap ping.
But if ping_host.nasl says that the host is dead, nmap ping will not
do better.

> After that it went off and found all the hosts successfully and
> produced an .nbe file. Then I 
> ran "nessus -i file.nbe -T text -o -" - zero hosts found!

> The .nbe file is 74K in size - I really don't think that's zero hosts! 
> There are "host_start" and "host_end" records for each of the hosts,
> and plenty of Security Note/Warning/<ahem>/etc - it all looks fine to
> me -
> but "Number of hosts which were alive during the test : 0"

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

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