Remote connection fails for WMI - RPC Error

[PeterR]

I have two Win2K3 servers and want to query WMI remotely. However I think
I've done everything to enable this, but it still fails with RPC server
unavailable error: 0x800706ba. I would appreciate some guidance as to what
else I can check. I'm using WBEMTEST for the testing. Here's what I have, and
where I've got to so far:

Server 1 is Win2K3 WEB. Server 2 is Win2K3 STD. Both are configured on a
private LAN with private IP addresses - no firewalls between machines or on
the machines themselves. There is no AD or domain environment. Both machiens
are members of the same workgroup.

1. I can interrogate WMI locally on both machines with no error
2. I can interrogate WMI remotely from svr1 to svr2
3. I *cannot* interrogate WMI remotely from svr2 to svr1
4. I have downloaded an run a wmi diagnostic vbs script - it tells me there
are no errors with WMI on either machine
5. I can use other services remote registry, remote administration, remote
event viewer from svr2 to svr1 - which I understand all use the same RPC
server.
6. I have been through and check permissions for remote DCOM
7. I have checked permissions for the WMI namespace - all identical on both
machines.
8. I have confirmed svr1 is listening on tcp/135 port - others too and
appear identical on both machines.

So I've spent hours looking for a solution, and have exhausted all checks
that I've managed to find so far - still without success. I figure there's a
simple solution.. bit I just can;t find it, and would appreciate any
suggestions as to how to proceed.

Thanks

[Gerry Hickman]

Hi,

It sounds like you have tested most things. Have you tried RPCPING both
ways? What does it say?

Post by PeterR
I have two Win2K3 servers and want to query WMI remotely. However I think
I've done everything to enable this, but it still fails with RPC server
unavailable error: 0x800706ba. I would appreciate some guidance as to what
else I can check. I'm using WBEMTEST for the testing. Here's what I have, and
Server 1 is Win2K3 WEB. Server 2 is Win2K3 STD. Both are configured on a
private LAN with private IP addresses - no firewalls between machines or on
the machines themselves. There is no AD or domain environment. Both machiens
are members of the same workgroup.
1. I can interrogate WMI locally on both machines with no error
2. I can interrogate WMI remotely from svr1 to svr2
3. I *cannot* interrogate WMI remotely from svr2 to svr1
4. I have downloaded an run a wmi diagnostic vbs script - it tells me there
are no errors with WMI on either machine
5. I can use other services remote registry, remote administration, remote
event viewer from svr2 to svr1 - which I understand all use the same RPC
server.
6. I have been through and check permissions for remote DCOM
7. I have checked permissions for the WMI namespace - all identical on both
machines.
8. I have confirmed svr1 is listening on tcp/135 port - others too and
appear identical on both machines.
So I've spent hours looking for a solution, and have exhausted all checks
that I've managed to find so far - still without success. I figure there's a
simple solution.. bit I just can;t find it, and would appreciate any
suggestions as to how to proceed.
Thanks

[Peter Rigbye]

Gerry,
Thanks for this. About the only thing I had not tried was RPCPing, as it
appeared to be more directed at testing Exchange communications and the IIS
RPC proxy components - none of which are installed or used in my environment.
I don't have the rpcproxy compnents on either machine as well.

So I've downloaded the ResKit now and tun it - but it's not obvious (to me
anyway:) )how to test basic RPCs for WMI usage. Using it with just the -s
switch tests successful in both directions.

Any other suggestions?
-----------------------

Post by Gerry Hickman
Hi,
It sounds like you have tested most things. Have you tried RPCPING both
ways? What does it say?