WMI authentication in a Workgroup....SOLUTION

coreymielke1013 · 2006-11-07T11:06:16.000Z

After disabeling the “forceguest,” setting in the registry Spiceworks
works in my home test workgroup!

Solution below:

Quote from:
http://groups.google.co.uk/group/microsoft.public.windowsxp.security_admin/msg/fa79ab12b3e2c2f8?dmode=source&hl=en

"It could be a ForceGuest issue…

Note that for Windows XP in a workgroup setting, default all connections
coming from “the network” will be authenticated as the Guest User.

Note that for WinXP Home you cannot disable the ForceGuest behavior
(only in WinXP Pro).

A direct registry edit is possible to change this setting:

HOWTO: Validate User Credentials on Microsoft Operating Systems

support.microsoft.com

Microsoft Support

Microsoft support is here to help you with Microsoft products. Find how-to articles, videos, and training for Microsoft Copilot, Microsoft 365, Windows, Surface, and more.

On Windows XP, the ForceGuest registry value is set to 1 by default in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

On a Windows XP computer that is a member of a workgroup:

If ForceGuest is enabled (set to 1), SSPI will always try to log on
using the Guest account.

If the Guest account is enabled, an SSPI logon will succeed as Guest
for any user credentials.

If the Guest account is disabled, an SSPI logon will fail even for
valid credentials.

If ForceGuest is disabled (set to 0), SSPI will log on as the specified
user."

jamesthompson1901 · 2006-11-07T11:11:07.000Z

You’re the man!

jamesthompson1901 · 2006-11-07T11:16:13.000Z

Now I just need to get it to authenticate to the SBS Sharepoint
server… I get immediate failures to this server using domain name\user
credentials.

it instantly denies access.

coreymielke1013 · 2006-11-07T11:24:12.000Z

Attached is a .reg key you can import to turn off the ForceGuest option.

USE IT AT YOUR OWN RISK!!!

TurnOffForceGuest.reg (254 Bytes)

samueldrayton · 2006-12-13T08:18:34.000Z

If you’re using SBS in a workgroup situation then you shouldn’t be
putting in a domain for logging on. Enter the username and password
identical on the server and you should be able to log in.

Let me know how you get on

joemotz · 2006-12-27T10:39:36.000Z

Very nice Jay Rod Ray Rurardo. That worked like a charm.

parley8418 · 2007-01-09T06:27:47.000Z

This needs to be built into SpiceWorks and put on the front page of trouble shooting this problem. It had never occurred to me that the XP Home would be the problem.

GREAT WORK!!!

woodman9964 · 2007-01-10T10:26:05.000Z

Thank you Thank you Thank you, This works great! Now I’m a happy guy!

michaeld8919 · 2007-02-28T11:06:39.000Z

Works like a champ. Thanks!!! I had the same problem with Windows XP Pro.

limhongyaw4129 · 2007-03-19T04:43:14.000Z

Hi there,

My company networks run in workgroup.
And I did try up the method above and it works and detected the XP Pro Pc. ( can’t detect XP Home, right?)
However I found one problem, if the computer is a print server (physicall connect to printer and share to others), user were unable to send to this printer anymore. It wil display access denied at the printer status windows.

Only I enable back the forceguard to 1, other users can print to that printer.

I would like to know how can I accomplish 2 task (detect XP PRo PC) & (Share out printer) or other alternative i can keep the user happy ?

Pls advise.

db47398 · 2007-03-21T01:08:14.000Z

I am new to this and obviously doing something wrong. I have 4 PCs and a MAC on the workgroup network. PCs are running XP Home. I have applied the .reg key and turned off the firewall momentarily but I am still getting password or WMI failures. I have double checked that the password is correct.

Any ideas where I ought to be looking for the problem, please

antigonetra8357 · 2007-04-02T07:52:21.000Z

Still trying, here!

I’ve checked one of the two computers in question…

ForceGuest is set to 1, the Guest login is enabled, and the OS is XP/Pro.

But I’m still getting the WMI error … Any more hints?

Antigone

justindorfman2891 · 2007-04-02T10:07:17.000Z

I <3 you. Thank you I was ready to pull my hair out if I saw another ‘WMI Error’.

vetclinic5405 · 2007-04-08T11:38:09.000Z

This was exactly what I needed. Thank you very much Jay.

frap0319 · 2007-04-12T15:36:40.000Z

db, this solution will not work with XP Home. Only for XP PRO.

Thanks for the solution, I am on a domain so it doesn’t apply to me, but it’s people helping people that helps get things done around here.

chris1296 · 2007-04-13T08:28:09.000Z

Jay, you’re the hero!!!
That worked for me! I was shortly before giving up! Thanks a lot!
Chris

walterp1774 · 2007-04-20T10:51:22.000Z

Hi!

I have a similar problem:

In our company we are mostly in a Windows Domain, but some computers are in a workgroup. We can monitor those on the Domain but Spiceworks does not recognise or monitor the ones on the workgroup

What to do?

Thanks in advance

W.

Harold-Spiceworks · 2007-05-11T13:02:04.000Z

This is how to set the forceguest option on WinXP Pro without editing the Registry (this is for computers in a Workgroup).

Start > Control Panel > Administrative Tools > Local Security Policy
Security Settings > Local Policies > Security Options.

3 Find ‘Network access: Sharing and security model for local accounts’, right click and select properties.\

Set the option to ‘Classic - local users authenticate as themselves’

charly1115 · 2007-05-11T13:33:47.000Z

I tried but i get the error below after changing the FORCEGUEST:

Test Failed: ConnectServer OLE error code:800706BA in SWbemLocator The RPC server is unavailable. HRESULT error code:0x80020009 Exception occurred.

I can see the computer in my explorer and access his files.

charly1115 · 2007-05-11T14:19:28.000Z

Thanks guys, I resolved it with

netsh firewall set service REMOTEADMIN enable (at command prompt) is a firewall XP SP2 issue