1

Hello there! This is my first time posting to the community!

We have been running Spiceworks in our network at least 2 years. We love it! But Spiceworks hasn’t been scanning recently. We’ve got some new hardware on the network but it hasn’t shown up. I manually start a scan, it will start for seconds but then abruptly stop. I’ve upgraded to the newest version and we’re still having the same problems. Help!

1 Spice up
2

Hello Robert,

Welcome to the community!

The second part is you may have to modify your scan range in Settings in order to include your new devices.

Since it seems to stop right away, you may want to completely delete the scan ranges and try to re-run the scans. if that doesn’t work, please post back so we can try a few other things.

3

I tried doing that and to no avail. I did however see the “test” scan range option and I did that. It notified me that it’s firewalled off. We just recently installed a new firewall so I think it may be in the way, I’ll dig deeper into this. :slight_smile: TY for your reply.

4

Could the password have been changed for the account that is listed in your Scan Ranges ?

5

CharlieB has the right idea. Check all of your authentications as passwords and even user accounts may have changed. Normally, the scan will continue despite firewalls and will go for longer than a few seconds or minutes unless the account being used has no access to WMI.

If you have changed servers, you might check the server’s firewall outbound settings as well and make sure it has complete access to your networks.

6

Hey guys so I deleted all my ranges and re-created one. I’m having the same problem. It will start to scan then stop. We haven’t moved servers, and the authentication is same.

7

Have you reviewed your log files within Spiceworks? Bottom page of your network scanning page has a link to view the logs…

8

Hi Tynen, Please set your Scan Speed to “slow” and initiate a network scan. Once it stops then navigate to your Spiceworks install directory by default C:\Program Files\Spiceworks and create a zipped log file package by clicking on spiceworks_package.exe

Send this package to support@spiceworks.com referencing this thread and we’ll take a look at this. Let me know if you have any questions!

9

Somehow our installation got marked as a remote collector. It’s flipped back to normal. And working! Thank you Spiceworks! :slight_smile:

In the web ui it didn’t know it was configured to be a remote collector, but in the settings.yaml file it was configured to be a remote collect. Flipping that setting to false made spiceworks work again!!