1

How do I fix this? Tried the Enable DCOM thing, tried the WMI settingg, nothing worked, I’m about to give up on this. Thanks

2 Spice ups
2

I’m sorry for your inconvenience

My first question, are you in a domain or workgroup environment?

Test your connectivity by typing the following command from the command prompt (Start Menu → Run → cmd.exe). This procedure needs to be performed from the computer that Spiceworks is installed on, and to the remote computer.

wmic /user:USER_NAME /password:USER_PASSWORD /node:IPADDRESS systemenclosure get serialnumber

USER_NAME = the domain account (DomainName\UserID) or local account (UserID) entered in Spiceworks

USER_PASSWORD = the password for the above account

IPADDRESS = ip address of the unknown device

This should return the serial number of the machine that you provided an IP address for.

The following examples are successful wmic responses:

SerialNumber
4HC2691

or

SerialNumber
None

Also, please do a forward and reverse lookup to the machine in question

nslookup IPADDRESS
nslookup HOSTNAME

Please let me know the outcome.

NOTE: Do not enter any network specific data

3

Dear myshell, I am getting the same problem with three of my computers (two dells and a sony laptop - I saw a post where one guy seems to think the dells may cause the issue).

Anyway, I tried the “wmic /user:USER_NAME /password:USER_PASSWORD /node:IPADDRESS systemenclosure get serialnumber” bit and got an Access is Denied message.

Any ideas?

4

Hi Coot,

First verify that the account that you are using in Spiceworks is in the Administrators Group.

To verify this: Administrative Tools > Computer Management > Local Users and Groups > Groups > Administrators.

If that checks out take a look at the following help pages and post back your findings.

Is My Firewall Getting In The Way?

Setting WMI Namespace Security

Setting The Default DCOM Properties And Security

5

Yes, the account is already a local Administrator. The setup on these machines are no different to the others that are working.

I had already turned off the firewall and tested and it still didn’t work so not that.

I followed the guides for the other two that you listed but all the settings were already set correctly.

Help! I cannot see what is different on these machines compared to any of the others that work!

6

Is this a workgroup or domain? What is the OS of the machines that are working / not working?

7

All the PC’s are setup the same, with the same local Administrator username and password. All are Windows XP and all are in a workgroup.

When I say all, I mean both the working and non-working computers.

Regards…

Karl

8

I have the same error message when scanning a win 2003 server using SW 3 Beta.

I can however scan the same server successfully when using SW 2.1

Any suggestions?

9

Coot:

Since you say you are not running a Domain Controller (only using workgroups) then you likely have an issue with the workstation’s external authentication setting. Harold (from spiceworks) posted the fix for this problem in another thread for XP Pro workstations (you may have to scroll down to near the bottom of the thread):

http://community.spiceworks.com/topic/1575#entry-49010

I run a DC but had one PC that was using a workgroup and that solution was EXACTLY what fixed the problem. DCOM and WMI were properly configured but a WMI request accross the network in DOS would always fail. This change resolved that problem instantly and then spiceworks was also able to log into the PC.

If you have XP Home workstations then there is (reportedly) a resgistry hack that will let you change the ForceGuest registry setting to 0 in order to allow external logins to use user accts on the XP Home box (and then Spiceworks can log in) at the following thread:

http://community.spiceworks.com/topic/578

Good luck.

Kevin

10

Thanks for the tip Kevin but that didn’t work either.

For the record, all computers are XP Pro.

Do any of the Spiceworks team have any more suggestions?