1

The machine that spiceworks sits on is unscannable and has duplicated itself /w the same IP. This machine had been scanned fine before and out of the blue it just decided to have issues. The page says “Spiceworks has been trying to log into this device for a month with no success” which is BS because it was in inventory just a few days ago. The machine does nothing except run spiceworks and has not had a single configuration change on it.

I ran all of the "netsh" commands from the /fix page, which did nothing. I ran the Unknown assistant which couldn’t find any problems. I even have all of the group policy recommendations for an AD environment in place. It’s using windows firewall(disabled) and I double checked to make sure the machines PTR and A records are correct, so what the heck?

1 Spice up
2

Sho’Nuff! … er, Hey Jacob. Sorry, the icon threw me.

So when Spiceworks scans it’s host, it should use 127.0.0.1. Is the device a multi-homed device?

It might be picking up a secondary IP address. Or it could be a DNS entry that doesn’t match the hostname of the SW machine pointing to it’s IP.

Can you run any WMI queries on the Spiceworks host locally?

3

Nope the device only has one IP. I checked DNS, there is only one A record for the machine “SPICE-PC” and one PTR record for its IP. I logged on to the machine /w the spiceworks user credentials and ran “wmic systemenclosure get serialnumber” successfully.

4

I’d like to get a look at your logs to see what’s going on. You should receive an email from support@spiceworks.com with instructions on how to get those packaged up and sent in. Once I’ve gotten a look at those, I can make a recommendation.

5

Thanks! Logs sent over.

1 Spice up
6

Sorry about that, I turned on verbose logging. You should have the new logs.

7

Hey Jacob,

I never got the verbose logs, and the case auto-closed on my end. If you’re still having trouble, let me know and we’ll get things rolling again.