More fun with scan errors

edlee0063 · 2010-01-08T15:04:42.000Z

Hi folks:

I’m adding additional devices to my Spiceworks network scanning ranges, and running in to problems with my most recent additions. All are on a domain, using a domain-level admin account to login for WMI information. I’ve recently changed the hostnames on these machines, and rebooted to have them take effect. Active Directory correctly reports the new names.

Spiceworks is reporting that there’s an authentication error for each of these new machines. They are pingable, and I can use a wmic command from my Spiceworks server to correctly receive wmi information (I’ve been using the get serialnumber one suggested in the documentation on Scan Errors). I can even use Spiceworks to test the account against each machine, and every test is successful.

Any ideas where I might look next?

akp982 · 2010-01-08T15:06:01.000Z

Timeouts, change your scan speed to slow

edlee0063 · 2010-01-08T15:09:45.000Z

Testing that now. I’ll also add that Spiceworks is reporting the wrong hostname, although I’d imagine THAT is because DNS hasn’t caught up yet.

edlee0063 · 2010-01-08T15:18:04.000Z

That wasn’t it. Further, when I went to edit the login accounts being used for the network scans, Spiceworks sat there for a long time without loading any information. Then I refreshed the page, and the accounts were gone! What the heck?

edlee0063 · 2010-01-08T15:34:38.000Z

Well, go figure. I re-added the domain admin account, and now they’re scanning just fine.

What would cause Spiceworks to go crazy and lose network scan account credentials like that?

akp982 · 2010-01-21T06:55:20.000Z

Just because it can i suppose?

edlee0063 · 2010-01-21T12:30:35.000Z

snicker That’s as good an answer as any other.