WMI RPC Server not available

[John]

Hi.

I hope this is the correct group to post this query to. If not I apologise.

I occasionally use WBEMTEST.exe to check patchstate on individual machines
where SMS reporting is quirky. When I try to run this tool against a remote
PC, some of them give me an RPC Server is unavailable error when I attempt
to connect using \\PCName\root\cimv2. The Error number is 0x800706ba and
Facility is Win32

all my clients are WXP with SP2. (If I run WBEMTEST locally, it works as
expected.)

This has something to do with the Firewall settings on SP2. I assume a port
needs to be opened. I already have 135 and 445 opened for internal subnet
use. If I stop the Firewall, i can then connect remotely

Can anyone tell me the one I need to enable? (I have tried this with a Group
policy, but some machines work, others don't, yet the GP is being applied
successfully to all machines, as other changed made by the GP are visible).

Thanks

john

 

[Peter Falz]

Hi John,

Take a look at:
http://groups.google.de/groups?q="[email protected]&rnum=3

HTH

Bye
Peter

 

[John]

Hi Peter.

Don't think that really covered it. I have WinXP SP2 clients. Firewall is
configured using a GPO to enable the Firewall and set up a few port and
program exceptions. Included in this are ports 135 and 445

when I run wbemtest I connect to \\pcname\root\cimv2. In the past this
always worked, regardless of OS when I attempted to connect remotely to a
machine using thie above connection string. Once connected I would put in a
query of "Select * from Win32_atchstate where status = 'Applicable' to showe
me the patches that were still outstanding on that PC.

Since installing SP2, this now does not work for XP SP2 machines, but does
for W2k and W2k3 servers.

Not sure what I'm missing, I thought opening 135 would sort the problem but
it doesn't

Regards,

John

 

[Peter Falz]

Hi John,

Don't think that really covered it. I have WinXP SP2 clients. Firewall is
configured using a GPO to enable the Firewall and set up a few port and
program exceptions. Included in this are ports 135 and 445
when I run wbemtest I connect to \\pcname\root\cimv2. In the past this
always worked, regardless of OS when I attempted to connect remotely to a
machine using thie above connection string. Once connected I would put in a
query of "Select * from Win32_atchstate where status = 'Applicable' to showe
me the patches that were still outstanding on that PC.

What is "win32_atchstate"? Or do you mean "Win32_PatchState"?

Since installing SP2, this now does not work for XP SP2 machines, but does
for W2k and W2k3 servers.

SP2 for XP changes many settings.

I had pasted in the past the following posting. You see it as answer to the
question in the link:
http://www.eggheadcafe.com/ng/microsoft.public.dotnet.framework.wmi/post20236130.asp

HTH

Bye
Peter

 

[FunkZ]

Try this

http://tinyurl.com/d5bqy