On Mon, 2004-05-03 at 12:23, Do Van, Tan wrote: > On Fri, 2004-04-30 at 16:07, George Theall wrote: > > The trace suggests you're calling the plugin by invoking nasl at the > > commandline. If so, realize that this method doesn't give plugins > > access to KBs, which plugins such as this require. > right - I've re-run the scan using the client and get the same output.. > not vulnerable && it should be reported as vuln. > > here's the content of the kb: > 1083593490 3 Launched/10180=1 > 1083593490 1 SentData/10180/INFO/1=The remote host is up > 1083593490 1 Success/10180=1 > 1083593491 3 Launched/10330=1 > 1083593491 1 SSL/password= > 1083593491 3 Launched/12204=1 > 1083593491 3 Launched/11011=1 > 1083593491 1 Known/tcp/139=smb > 1083593491 1 Services/smb=139 > 1083593491 1 SentData/11011/INFO/1=An SMB server is running on this port > > 1083593491 1 Success/11011=1 > 1083593491 1 SMB/transport=139 > 1083593491 3 Launched/12209=1
find the answer... the target needs to talk smb over tcp/ip 445/tcp (instead of netbios over tcp/ip with 139/tcp). next time, I'll read more carefully the plugin name before 8^) _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
