WMI Problem in Workgroup Win 7

billchz · 2012-11-19T14:20:58.000Z

8 of these Windows 7 32bit 64bit & machines in a workgroup were working nicely in Spiceworks until last Thursday morning when the notification “Authentication failed because no Windows account was specified” on a single day just like that.

What i did;

Opened network Scan settings and run a test using the User Account that has Admin rights. But the Accounts were all failing giving out the “Test failed: check account, password or WMI configuration”.

2.Double checked WMI & Dcom settings as well as Kaspersky firewall and tested still but no joy.

Went to the SW main install and opened CMD then ran the WMIC get serial number then it returned an error

Node - xxxxxx
ERROR: 0x8007005
Description = Access is denied.

win 32

Tried different notes on WMIC 0x8007005 resolving but no luck.
Run WMIDIAG and got

30 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found

Tried to fix it using the winmgmt /resyncperf & /syncperf but there is no luck.

Downloaded and ran the Rebuild WMI script and then restarted the computer. Ran WMIDIAG again but same results all together without changes.

I wonder where am i going wrong and was it Windows updates or what that changed overnight hidden attributes of my setup. Any leads will be helpful on this guys.

Brendan-Spiceworks · 2012-11-19T15:53:58.000Z

Is it possible the user account you created on the workstations for the scan has an expired password?

Reset the password on one of the workstations to the known good password on the Spiceworks scan range and test again.

Let me know what you find!

billchz · 2012-11-20T05:20:25.000Z

Hie Brendan; I Opened some of the Network Scan accounts and retyped the working password and saved then test the account against the corresponding computer but same results “Test failed: check account, password or WMI configuration” thanks for replying.

Brendan-Spiceworks · 2012-11-20T13:34:53.000Z

Hi Bill,

Can you log into the workstations with the Network Scan account?

Did anything in the environment change (new firewall or AV software, for example?)

That they all stopped working on the same day made me wonder whether the workstations were configured with an account to be used for network scanning, and that account’s password expired.

Let me know what you find…

billchz · 2012-11-20T14:17:46.000Z

The odd thing is there isn’t something out of the ordinary only windows updates, no new software installed or tweaked. The computers respective user accounts with Admin rights can still log in without any problems with the same credentials. Will continue to compare any common Update or specific anomaly.

Brendan-Spiceworks · 2012-11-20T14:25:45.000Z

Hi Bill,

I might be misunderstanding you, but I want to make this point another time (dead horse and all that.)

Do all of the workstations have a common administrative account (like username = spiceworks) with a password configured, and has that same common account been used as the credentials for the Spiceworks network scan?

billchz · 2012-11-20T14:42:15.000Z

No its not one account. Different Admin accounts for computers and scan ranges have been created in Spiceworks to use them corresponding with their respective computers.

Brendan-Spiceworks · 2012-11-20T14:59:45.000Z

If it’s possible, it’d make management a lot easier for you if you could create a single account with a strong password, make the account a member of the Administrators group, and then configure Spiceworks to use that single account.

billchz · 2012-11-20T15:07:45.000Z

Sounds like a good idea Brendan, i will create an account profile on every computer but yet same username & password and update you tomorrow.

billchz · 2013-04-02T11:27:33.000Z

All problems were resolved just by installing a fresh copy of updated Spiceworks 6.2. I can read all the computers easily without issues. Thanks to all of you guys for the assistance.