Re: Netstat scanner does not seem to work on windows systems

Patrice Arnal wrote:
> It worked 2 months ago against windows :
>
> > results|sxb.bsf.alcatel.fr|frillsdmzg4.sxb.bsf.alcatel.fr|general/tcp|11936|Security
> >  
> > Note|\nRemote operating system : Microsoft Windows Server 2003 Service 
> > Pack 1\nMicrosoft Windows Server 2003 Service Pack 2\nConfidence Level 
> > : 59\nMethod : SinFP\n\n \nThe remote host is running one of these 
> > operating systems : \nMicrosoft Windows Server 2003 Service Pack 
> > 1\nMicrosoft Windows Server 2003 Service Pack 2\n
> > results|sxb.bsf.alcatel.fr|frillsdmzg4.sxb.bsf.alcatel.fr|general/tcp|19506|Security
> >  
> > Note|Information about this scan : \n\nNessus version : 3.0.5\nPlugin 
> > feed version : 200706190315\nType of plugin feed : Registered (7 days 
> > delay)\nScanner IP : 155.132.18.22\nPort scanner(s) : netstat \nPort 
> > range : 0-65535\nThorough tests : no\nExperimental tests : 
> > no\nParanoia level : 1\nReport Verbosity : 1\nSafe checks : 
> > yes\nOptimize the test : yes\nMax hosts : 1\nMax checks : 4\nScan 
> > Start Date : 2007/6/20 16:16\nScan duration : 885 sec\n\n
> ( excerpt of the nbe report )

The Nessus scan may have found open ports from other plugins, and also
reported that the "netstat" scanner was configured, but the netstat
plugin does not run on Windows. If you had that same scan configured and
disabled the netstat port scanner, you'd likely get the same results for
 your Windows systems.

Ron Gula
Tenable Network Security
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus