1

We had the Spiceworks agent installed on all our local machines until our network traffic began to spike big time, and I found some documentation saying that the agent should only be used on devices that go off-site. We uninstalled the agent from all our local workstations, but there are a stubborn handful that we can’t get on to the scans. There are 3 categories these problems fall into:

  1. No open ports for the device were found to be responding. Most of these machines show as offline even when they’re online. I have tried every fix I could find on Spiceworks (we have the Windows firewalls turned off and are on a domain, but I still tried the Firewall rules, WMI fixes, and rebuilding the WMI repository) but these same few machines will not get on to the scans.

  2. A second device with the same name and ip address as a working device shows up. I get an error every time I try to tell Spiceworks “This is a different device I’ve already scanned in”. I tried deleting just the bad copies of these devices, but they show up again on the next scan. I tried deleting the bad copies and the good, but they both show up again on the next scan.

  3. My favorite, the mystery error! See attached screenshot, but basically it says “We couldn’t connect to the device due to the following error:”. That’s it, no error. I’ve tried all the WMI and firewall fixes I could find for these. I tried logging on to these machines and going to the spiceworks fix page, but these ones don’t show up there.

Can anyone help? I’m feeling really silly after spending multiple days trying to resolve the handful of errors on our network and making no progress. Thanks for reading.

spiceworks_mystery_error.png
spiceworks_mystery_error.png1024×622 262 KB
4 Spice ups
2

I think we’re just going to skip ahead to a support ticket. Please watch for that email.

3

Thank you, Chad! I’m getting those log files together now to send to you.