> >> Okay, turned "Launch Nmap for Network Scanning" on and "Nmap (NASL > >> wrapper)" > >> off, pointed it to a single IP with known services exposed, and it still > >> finds none of them. > > I'd say "Openvas TCP Scanner" is more likely to work than the network scan > > nmap.
To clarify, I meant in Whit's current situation Openvas TCP Scanner would be a better try than the network nmap scanner. > So in order to perform a reliable port SYN Scan with pings which one > should we use? OpenVAS TCP Scan, OpenVAS SYN Scan, Nmap wrapper, or > "Launch Nmap for Network Scanning"? >From what I can gather the usual Nmap wrapper port scanner is best for any type of scan. > Before "Nmap wrapper" was the only one using nmap. But now there are > two. I don't understand the second. The second one is a new one, experimental I think, that does the entire network scan upfront, instead of calling nmap for each host. -- Greenbone Networks GmbH Neuer Graben 17, 49074 Osnabrueck, Germany | AG Osnabrueck, HR B 202460 Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
