Jim: I /think/ what you're looking at is a nmap problem. While I make no claims to be a Guru with SuSE (being a Solaris guy), I know that nmap output being off has causes nessus to miss things in the past.
Are you running the latest nmap? Thanks, Joshua Knarr -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Klun, Jim Sent: Friday, December 05, 2003 1:22 PM To: '[EMAIL PROTECTED]' Subject: SUSE 9.0 problem Our group has been using nessus successfully for some time. We recently started using SUSE as our favored linux distro. All was well until we started using 9.0 - I can get get 2.0.9 nessus to complile using installer.sh but usage results are not consistent. Fell back to 2.0.7 - same results. Using SUSE 8.0 on a different partition on the same machine, 2.0.9 works fine Others in my group are having same experience. We have enough experience to tweak the various prefs/scanning options in the past and get what we expect - but with 9.0 we are stumped. Examples: Messenger service nasl 11890 finds no vulnerable hosts on a class C with SUSE 9.0 but 10 with SUSE 8.0. Sames settings for scan. Nessus probe for SSH finds ONLY the scanning box itself with 9.0 - finds all the known port 22 listeners with 8.0. ( 5 boxes ). Nmap itself works consistently across 9.0/8.0. Is there a known problem with SUSE 9.0 in regard to nessus - I can find no mention in the archives. _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
