1

I have a number of devices, mainly printers, which are online and yet Spiceworks will not scan them. Every time I initiate a manual scan, it goes through the network search process but does not actually update the “Last Scanned” time. There are no duplicate entries for these devices and they are definitely online (with static IPs). Are there some log files somewhere that I could check to figure out why Spiceworks can’t “see” these devices? It also should be noted that the “Last Updated Time” is current, but the “Last Scan Time” is off by a month or more in some cases (even though I have weekly automated scans set up for all my IP ranges).

There are also some devices with a scan time of today (7/31/2013) that are still in the “Not Scanned in 30 Days” Group. Is there a waiting period before those devices leave the group automatically, or do I have to remove them manually?

7 Spice ups
2

I’ve found that sometimes when making updates on scanned objects it takes a couple minutes for it to be updated in the “last scanned” and the “not scanned in 30 days” groups. On the “not scanned in 30 days” do a search for one of the IP’s that is on a device in there and make sure it is not assigned to another machine as well. Reverse DNS can be a problem and NSLookup is also useful in troubleshooting that.

Printers, in my case, are fickle group of devices. Some of the devices scan, but others will not. For example, the MFP does not scan and one of our old print/scan printers. Then there is another printer that says it is low on ink, but it actually has almost full ink. I wonder if spiceworks is going directly to the devices to find this info or if it is getting it from the print server…

1 Spice up
3

Hi Chris,

Generally, when troubleshooting a scan issue you’ll want to look at the finder_child logs for network scan logs. If you rescan an individual device, however, you’ll find the info in the finder_re log.

If the device has been scanned within the last 30 days, it should be removed from the group automatically. Since the “Last Scan Time” is off, that’s likely why you’re still seeing them within the “Not Scanned In 30 Days” group.

I’d like to get a peek at your logs so we can figure out what’s going on, so I’ll get a support ticket created for you. Be on the lookout for an email from us!

1 Spice up
4

Hey Calvin–

Yeah it looks like some of the devices have begun to remove themselves from the group. Some move quicker than others, but it does eventually update.

2 Spice ups
5

Thanks to both Calvin and Jon for their assistance. It looks like the scanning problems are related to DNS issues on my end (which will just require some reverse lookups to be added). I also enabled SNMP on the printers and that seems to make things go much better.

2 Spice ups
6

Glad you found what you needed and glad to be of assistance!

7

I’m coming across what appears to be the same thing.

What reverse look ups were added?

8

One slightly annoying but fairly simple fix I’ve found for this is to navigate to the device in SW, click “Edit”, remove the group “Not Scanned in 30 Days” and it will go to the manually excluded list right below that. Then remove it from the manually excluded list and it will go back into the “Matched rules in” group. Click “Save”. You will then see that it’s completely gone.

2 Spice ups
9

This doesn’t actually resolve the issue of the device not scanning. This would just remove it from the list

10

Thanks for confirming molan. It’s actually worked for me, but it sounds like it’s a slightly different issue. My problem has always been that my devices are successfully scanning, but they still show up as “Not Scanned in 30 Days”. Performing the steps I listed has sort of “cleared” the “stuck” scan status.

2 Spice ups
11

Shuey, it works! AMAZING!

Even though I hit the X when it’s in the excluded and it jumps back to the “not scanned in 30 days” it VANISHES when I hit SAVE!

Thanks! I had so many computer that couldn’t be scanned because they were “STUCK” in NOT SCANNED in the 30 days group. EVEN though it COULD be scanned (not a login error).

1 Spice up