Asset Discovery Strange Results

(imported topic written by SystemAdmin)

We have a scheduled scan created using the Asset Discovery NMAP Wizard that runs repeatedly which we thought we thought was working correctly. This scan has a bunch of different ranges of ip addresses that it is scanning. We noticed a few pc’s we were testing were not showing up in the scan. We confirmed the computers were on when the scan ran. We set up another scan using the Run NMAP scan fixlet that targeted just that subnet where the computers were located and they then showed up.

I’ll be digging through the logs later, but was just curious if anyone else had run into this problem?

(imported comment written by BenKus)

Was the scan coming from inside the subnet? Sometimes the routers strip some information if you scan across subnets…

Ben

(imported comment written by SystemAdmin)

Hi John,

I have noticed the same behaviour. The scan does report all the attached assets on the subnet in the nmap xml file but the importer doesn’t always seem to add them into the DB correctly.

As per my similar post:-

Pulled out hair, gnashed teeth --> Result : went to pub for lunch and a pint :wink:

(imported comment written by SystemAdmin)

@ben - the scans were on a different subnet from the same endpoint.

@cidemark - Guess I didn’t follow through on my previous commitment to use your technique! Are you still seeing the behavior or is it working - as indicated in your previous post?

(imported comment written by SystemAdmin)

Occasionally - but I don’t run nmap scans on a regular basis.