When using Nessus 3.x, either with nmap or without, it fails to pick up
all open ports on a host even if the port_range variable is set to
1-65535. When nessus 2.x scans the same exact host, even with the
port_range variable set to default, it picks up the open ports. The
specific example we have been using for our testing is psyBNC, but it is
not currently throwing a banner. Nessus 2.x is currently picking it up
as being an unknown open port, but not psyBNC, because it is running on
a non-standard port and has no banner (this is expected), however,
Nessus 3 does not show the port as being open at all.
Is this the correct way in which Nessus 3 is supposed to work? (not
showing a port unless it can grab a banner) If so, can we change this
behavior? If not, is there a setting we can check/change that may
alleviate this problem?
Regards,
Kenneth Shelton
Incident Response Team
University of South Florida
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
