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

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).

In the end I had to turn off both tcp and icmp ping options and 
configure it to use the nmap scanner option. 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"

This is Nessus 2.2.4 run on several different systems. I even tried 
loading the nbe into Nessus GUI - empty report :-(

It looks to me like Nessus looks for something specific in the nbe file 
to tell it that a host is alive - and it isn't there?

Any ideas?

--
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