F-Secure Radar Discovery Scan not finding any hosts - F-Secure Community
<main> <article class="userContent"> <h3 data-version="8" data-article="000007245">Issue:</h3> <p>F-Secure Radar Discovery Scan not finding any hosts</p> <h3>Resolution:</h3> <p>General instructions for troubleshooting:<br></p><ul><li>Keep "Process if no PING" option turned on.</li><li>Create a new Discovery Scan template, port scan mode i.e: for TOP 100 ports and with debug / verbose mode enabled. Attach your newly created DS template to your new discovery scan record and run it. This will tell you much more about the details of the scan execution and can enclose the root cause.</li><li>Check gateways. In case the scan node server has more than one network interface / IP address, check if the scanner can for some unknown reason choose another gateway.</li><li>On the "Scanning Performance" drop-down, try choosing "polite" or "sneaky".</li><li>Don't only ping the given host (i.e. 192.168.99.71) from the scan node. Try to also access some services (f.ex: if there is a www service, try to access it with a web browser from the scan node). <ul><li>Consider checking what account with what type of permissions you are running. Are your local account permissions the same as the permissions of the service account that Radar scan node is using?</li><li>If your user account is coming from AD, while Radar has a local user account - does it change anything in your network setup with regards to what you can / can't access over the network?</li></ul></li><li>Radar uses Nmap for port scanning, which is an industry-standard tool. You can see the exact command line parameters in the scan log that Radar uses to run a specific port scan. You can try to download namp <a rel="nofollow" href="https://nmap.org/download.html">https://nmap.org/download.html</a>, run a port scan using nmap GUI, and compare command line params and results. </li><li>Check the system proxy settings. Notice that the proxy settings can be different for the Scan Node Agent service account (local user?) and for a personal user account that is coming from AD.</li><li>In some scenarios, disabling ARP-ping is required to allow the scan node agent installed in the same subnet to find hosts. To edit an existing discovery scan template (host discovery or port discovery), use the instructions below:</li></ul><ol><li>Create new discovery scan template.</li><li><span style="font-family: arial;">Name it as you wish (eg. "Host Discovery (no ARP ping)")</span> or from the <span style="font-family: arial;">scan mode select "Host discovery" or "port scan".</span></li><li><span style="font-family: arial;">Click Finish and Save.</span></li><li><span style="font-family: arial;">Download the new template by s</span>electing it on the templates list (click on the checkbox).</li><li><span style="font-family: arial;">Click "Download scan settings".</span></li><li><span style="font-family: arial;">Edit the downloaded file by adding ' --disable-arp-ping' node within '' (see screenshot).</span></li><li><span style="font-family: arial;">Click "Upload scan settings' on the Radar templates list.</span></li><li><span style="font-family: arial;">Browse for your edited file and click "Upload."</span></li><li><span style="font-family: arial;">Use your new template in discovery scans.</span></li></ol><img alt="Editing the default scan template to disable ARP Ping" height="336" src="https://us.v-cdn.net/6032052/uploads/914/4VWA5SYT7HEF.png" width="500" class="embedImage-img importedEmbed-img"></img><br><br>If none of the above helped, you should re-install Radar discovery scan node. <p>Article no: 000007245</p> </article> </main>
