WMI win32 access denied workgroup NOT domain 'microsoft you're killing me!'

O.K., desperation time, before I start I am not talking about a Domain
here. I am only talking about a simple home workgroup. I have WMI
security working without trouble at work in our corporate domain, but
can't work out why I can't get it to work at home where I do not want
a domain. Here is my problem. If I use [Computer
Management][Services and Applications][WMI] and bring up the
properties on a local machine, it works fine. If ? however ? I
<right-click> on [Computer Management] and then connect to any other
computer in my workgroup; then attempt to get the properties of WMI, I
simply receive the message that "Failed to connect to <computer name>
because Win32: access is denied" I have made absolutely sure that the
local administrator's accounts are exactly the same name and password.
I have made absolutely sure that the remote machine's ?WMI Security
settings' for the local administrator are maxed out and inherited from
"Root" namespace down. I have tried many other bits and pieces, but
simply can't get this to work. In my Corporate Domain at work,
security is set through ?domain security objects' and I have no
trouble writing scripts that use WMI on remote machines. Just can't
get it to work at home and it is driving me crazy. Please any help on
what to try? Because I can't get the bloody authentication to work, I
can't get Microsoft's WMI explorer to return structures on computer in
my home network other than the one I am working on, which is really a
pain in the #$%^rse.

Torgeir
Sun Aug 15 08:14:30 CDT 2004

mark tognella wrote:

> O.K., desperation time, before I start I am not talking about a Domain
> here. I am only talking about a simple home workgroup. I have WMI
> security working without trouble at work in our corporate domain, but
> can't work out why I can't get it to work at home where I do not want
> a domain. Here is my problem. If I use [Computer
> Management][Services and Applications][WMI] and bring up the
> properties on a local machine, it works fine. If ? however ? I
> <right-click> on [Computer Management] and then connect to any other
> computer in my workgroup; then attempt to get the properties of WMI, I
> simply receive the message that "Failed to connect to <computer name>
> because Win32: access is denied" I have made absolutely sure that the
> local administrator's accounts are exactly the same name and password.
> [snip]
Hi

I'm not so sure that it helps that the username/password is the same,
because it still different users (different SIDs).

Most likely you need to connect with explicit user credentials, use
SWbemLocator.ConnectServer instead of GetObject("winmgmts:...")

IWbemLocator::ConnectServer
http://msdn.microsoft.com/library/en-us/wmisdk/wmi/iwbemlocator_connectserver.asp

Subject: Login with explicit username and password
Newsgroups: microsoft.public.win32.programmer.wmi
http://groups.google.com/groups?th=2b5bcad76f5debaa

Subject: ImpersoantionLevel other than impersonate
Newsgroups: microsoft.public.scripting.wsh
http://groups.google.com/groups?th=89ff50603f12dcfb


Also, if this is Windows XP computers, you might have a ForceGuest
as well.

WinXP in a workgroup setting defaults to authenticate all connections
coming from "the network" as the Guest User (only possible to change
on WinXP Pro).

More about this here:
http://groups.google.com/groups?selm=3E822EB9.C5D31E11%40hydro.com



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

togbabe
Tue Aug 17 05:54:50 CDT 2004

Thanks so much Torgeir. The XP Security Settings\Local
Policies\Security Options setting to Classic was the problem. What a
strange thing for Microsoft to use as a default. Talk about 'a needle
in a haystack.' Thank god you were there to read my post. Ta.

David
Tue Aug 17 20:17:12 CDT 2004

I assume this was happening on XP SP2?

Does it also work if you just run the following command?

netsh firewall set service type=remoteadmin mode=enable scope=all profile=all

"mark tognella" <togbabe@yahoo.co.uk> wrote in message news:3e1ebef8.0408170254.47ce9cf9@posting.google.com...
> Thanks so much Torgeir. The XP Security Settings\Local
> Policies\Security Options setting to Classic was the problem. What a
> strange thing for Microsoft to use as a default. Talk about 'a needle
> in a haystack.' Thank god you were there to read my post. Ta.