1

I have about 375 devices and around 300 of them (all windows computers) show last scan as 2/28/18. We have 4 scans that run a week of the entire network. It worked up until 2/28 and it is continuing to work for about 15 windows pc’s. When I run a scan it shows me this when it completes:

SWSCAN.jpgBut when I check 90% of the devices the “Last Scan time” shows 2/28/18

I have completely re-installed spiceworks on the server. I have scanned a device with firewall disabled and no AV running. The computers show last update as 3/25 or another more recent date and none of them have been manually updated. Meaning Spiceworks is still in contact and updating the device in Inventory. I can ping each device and nslookup comes back fine on the server to the device.

I have exhausted every resource to try and figure this out… Please someone help me :frowning:

3 Spice ups
2

Email support and have them take a look.

I’ve been through this a few times and it generally involved support, and also deleting inventory and starting again.

YMMV, and I’m eagerly anticipating a solution!

3

If they are windows 10 build 1709 they are not scanning currently.

I am guessing they are since you don’t give us that information. - Support are also aware of this

4

I have Windows 7-10 computers all doing this same thing.

5

Ping -a (one of the devices not scanning, but by their last known IP according to SW)

Ping -a 1.2.3.4 - does it return the same name as SW sees?

What SW version?

6

Returns same IP as spiceworks has in inventory

Spiceworks Version 7.5.00107

7

It is weird they successfully scan its just the “Last scan time” field states 2/28. I am wondering if they dont actually scan and it just says it successfully inventoried all of them but really did not… I dont know anymore… I’m emailing Spiceworks support logs for them to check out. Thanks for your help

8

It shouldn’t return an IP it should return a DNS name.

Last scanned time means it is NOT scanning it for some reason, be that windows firewall, WMI filter settings, wrong password or something is blocking it.

9

Checked credentials, turned firewall off on my test device, did nslookup from server and it came up with correct device, turned AV off. I would tend to agree but I have tried all of those already

10

I post to help, however your firewall, AV and nslookup are unlikely the cause unless you have changed the firewall, AV or have stale DNS records.

Add one device that is not scanning to the scan ranges by IP and disable all the other ranges - then set that one device scanning - does it pick it up?

nslookup is also forward DNS, it tends to be the rDNS that is stale - remember spiceworks scans by IP, not DNS name, so an IP will be looked up, matched then scanned, if you have stale DNS records then you could be scanning a different device.

11

I’ve tried scanning a single device. Also checked into the DNS and flushed it on the server with no problems. Its looking more and more like Inventory just isnt actually scanning properly.