RE: Nessus 1.3.4 NetBIOS tests.
"Zimin, Alex" <[email protected]>
| Newsgroups | gmane.comp.security.nessus.devel |
|---|---|
| Message-ID | <48FB76BF31A47C4B9893827DEDF7DF2A019FAA34@sacexch01.lan.towerrecords.com> |
I don't see anything unusual in the dump or messages files Nessusd.messages file has the following for the SMB tests: "Not launching smb_pluginname.nasl against xxx.xxx.xxx.xxx because the key SMB/login is missing (this is not an error)" It may explain why other smb plugins don't return results, however I don't receive results from smb_login.nasl plugin, which should not depend on SMB login info and should return me "NULL session" Windows vulnerability. Is it a problem with "smb_login.nasl" plugin? Alex. > > > Just verified with Nessus 1.3.4 from cvs and latest > > plugins, NetBIOS > > > tests on port 139 do not return correct results. Can anyone else > > > re-create the problem? > > > > new nessus increases paralallelism (runs faster) and might muck up > > netbios if you don't make sure you include 139 and 445 in the non > > parallel ports section of nessusd.conf: