Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | OS detection |
|---|---|
| Date: | Fri, 29 Oct 2004 11:29:42 +0100 |
Hello, I am running Nessus 2.0.12 with Nmap 3.7 and Mandrake Linux 10. I ran scans against a large number of systems recently, driven by target hosts files, and have found that the reports indicated the operating system for only ~20% of the target hosts scanned most of which are running Windows 2000. In most cases neither the Nessus nor Nmap operating system detection has reported anything. (Scans of the same set of hosts with earlier Nessus/Nmap/Mandrake versions identified the OS at least for ~all the Windows systems). However, when I ran a scan against a couple of the Windows 2000 systems (without changing any settings), that had been previously scanned with no OS reported, the resulting report this time included the OS. I seem to have a serious performance problem. Any ideas what is going wrong here or where to look? -- Carl Nelson Distributed Systems Support Section, Computer Centre, University of Leicester, Leicester, LE1 7RH, U.K. Tel: +44 (0)116 252 2060, Fax: +44 (0)116 252 5027 _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Running NASL on command line returns no results on known vulnerable scan, Erik Stephens |
|---|---|
| Next by Date: | RE: Turning on mem leak detection, Michael Scheidell |
| Previous by Thread: | Running NASL on command line returns no results on known vulnerable scan, Chuck Gwan |
| Next by Thread: | Re: Port scanning problems, Joshua Holland |
| Indexes: | [Date] [Thread] [Top] [All Lists] |