Hi, Many thanks for your explanations!
> nmap -sU -p U:$yourportlist $targetip I first did a scan with nmap -sU -p U:140-180 $targetip and nmap reported that all scanned ports are open|filtered. So I did a new scan with additional -sV and nmap found the SNMP service running on port 161. Back in OpenVAS, I created a new Port List with exactly the same UDP port range and no tcp ports. However, OpenVAS did not report the SNMP service. > this gives you already a pointer. In general it is recommended to > whitelist the scanning machine to avoid such issues while port scanning. I created a new rule in the Windows Firewall allowing all incoming traffic from the scanning machine. But the results remain the same! To crosscheck, I disabled the firewall and did the same scan again - and OpenVAS found the SNMP service. > It won't solve your issue but you should note that these are quite > outdated components of OpenVAS. Please update to the current components: > Libraries 8.0.8 > Scanner 5.0.7 > Manager 6.0.9 I will do this any time soon! > Both lists contain port 161? Yes, all the lists used contain port 161. Regards Daniel _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
