1

Spiceworks doesn’t seem to be finding new devices and isn’t scanning devices that have already been inventoried. I believe this started about 7/31/16 when I moved Spiceworks to a different computer. I moved it again this morning but the problem continues. I have 173ish devices in Spiceworks and 82 of them are members of the “Not Scanned in 30 days” group. Only two devices seem to be scanning these days. The rest either have no date of last scan or the date of last scan is 7/31/16.

I’ve removed all entries from the list of scan ranges. I added a single IP address entry for a Cisco Small Business Switch. Spiceworks seems to see it and puts a grey entry for it on the Scan screen but never does anything with it. I’m also running PRTG and it sees that switch through SNMP the way I’m trying to scan it with Spiceworks and PRTG inventories it and starts monitoring it with no problem.

The Windows Firewall on the current Spiceworks computer is off. Its running Windows 7 Ultimate with all the latest Windows Updates.

Could someone on the Spiceworks support staff take a look at my logs? I’ve been trying to resolve this off and on for a while but haven’t been able to make any progress on it and need to turn it over to a higher power. I’d appreciate any assistance you could provide.

2 Spice ups
2

I don’t think we need support to look at your logs at this stage, but if you have any IDS/IPS on the network and your SW server IP changed, you need to edit your settings to allow the new IP to scan, otherwise it will get blocked.

Also try this

Settings, inventory, device scanning - disable all ranges, restart SW

Add a single IP you know is online and ready, scan it, if this inventories re-enable the rest, if it does not let me see what you get

3

Thank you for your reply Rod-IT.

We don’t have any IDS/IPS on the network.

I have worked through the procedure you suggested. I actually used two devices that are online and ready. One of them is a laptop running Windows 7 Professional and the other is a Cisco Small Business SG300-10 switch with SNMP enabled.

Spiceworks seems to detect the devices but their entries turn gray on the Scan Overview page and they just sit there and nothing ever happens. They don’t show up in the inventory.

4

Grey indicates something blocking the port probes, it sees the device but it cant scan it because or something, new AV?

5

We have the same AV we’ve always had and I haven’t made any configuration changes to it. That’s what they all say though isn’t it.

One of the devices is a Cisco Small Business switch and it doesn’t have any AV. I’ve been able to add both of the test devices to PRTG and it seems them and adds them successfully. I use the same credentials for both PRTG and Spiceworks.

6

And this is why I asked about IPS/IDS, this would be based on IP.

The two products are not on the same box?

1 Spice up
7

How did you move SW?

Did you upgrade or change version during this process?

1 Spice up
8

I worked through this procedure both times: https://community.spiceworks.com/how_to/295-move-your-spiceworks-installation

I’ve moved it twice. In both cases, I upgraded Spiceworks on the production computer to match the version on the newly installed candidate computer.

9

So long as the DB and Data folders are from the same version this shouldn’t’'t be the cause, however if your DB/Data folders were from 7.5.00123 (example) and your new one is 7.5.098 then there could be issues between versions.

In your SW directory is a logs folder, take a look in ‘finder_discovery1.log’ for clues

1 Spice up
10

If you want me to look at the log for you, I can, but note on the public forum as it will contain your private IP ranges and devices names, but I am happy to look if you want me to in PM, I also understand if you’d rather not

1 Spice up
11

I reinstalled Spiceworks and did not restore the database. The new installation of Spiceworks took inventory and found everything successfully so I think the old Spiceworks database must have developed a problem during the first move. I’m not sure whether to try to fix the old database or just move forward with the new one.

I appreciate your help Rod-IT.

12

If you want the old fixing, support need to do this, editing the DB yourself is not supported.

I will tag support in here, if you don’t want them to look simply leave a note here, otherwise @jaimedelapaz will be in touch soon

13

I’m not Jaime and I don’t play him on TV, but I should be able to help out. :slight_smile:

It does sound like something is going on with the DB so I’ll shoot over some instructions on sending that over via email. Hold tight!

14

Jaime never gave me any info he would be away, otherwise you’d have been my target Jon :slight_smile: