PaulDotCom mailing list archives
Scanning for Confiker via nmap
From: paul at pauldotcom.com (Paul Asadoorian)
Date: Mon, 30 Mar 2009 14:47:43 -0400
If you are running Nessus using nessuscmd, here are some speed improvements: Original Command: ./nessuscmd -p445 -U -V -i 36036 192.168.1.0/24 real 2m25.456s Improved Command: ./nessuscmd -p445 -i36036 -omax_hosts=64 -o"Do not scan fragile devices[checkbox]:Scan Network Printers"=yes 192.168.1.0/24 real 1m49.195s I will post updated commands/settings as I get them. Cheers, Paul John Sawyer wrote:
The 3rd check in the Nmap script will not run by default because it is considered "unsafe" since it has the possibility of crashing machines. As for timing, I tested on a class C with 224 machines, 212 of which are listening on 445. Nmap with no timing options: done: 256 IP addresses (224 hosts up) scanned in 40.38 seconds Nmap with -T5 done: 256 IP addresses (224 hosts up) scanned in 8.94 seconds Nessus using the command you sent earlier. 2m36.659s
-- Paul Asadoorian PaulDotCom Enterprises Web: http://pauldotcom.com Phone: 401.829.9552
Current thread:
- Scanning for Confiker via nmap, (continued)
- Scanning for Confiker via nmap Tim Mugherini (Mar 31)
- Scanning for Confiker via nmap Nick Baronian (Mar 31)
- Scanning for Confiker via nmap Tim Mugherini (Mar 31)
- Scanning for Confiker via nmap xgermx (Mar 31)
- Scanning for Confiker via nmap Tim Mugherini (Mar 31)
- Scanning for Confiker via nmap Chris Merkel (Mar 31)
- Scanning for Confiker via nmap Paul Asadoorian (Mar 30)
- Scanning for Confiker via nmap John Sawyer (Mar 30)
- Scanning for Confiker via nmap Paul Asadoorian (Mar 30)
- Scanning for Confiker via nmap Jason Wood (Mar 30)
- Scanning for Confiker via nmap Paul Asadoorian (Mar 30)
- Scanning for Confiker via nmap John Sawyer (Mar 30)
- Scanning for Confiker via nmap Albert R. Campa (Mar 30)
- Scanning for Confiker via nmap Chris Merkel (Mar 30)
- Scanning for Confiker via nmap John Sawyer (Mar 30)
- FW: Scanning for Confiker via nmap Paul Asadoorian (Mar 30)