Page History

...

You can use the

To use WbemTest:

1. Run wbemtest.exe.
2. Click Connect.
3. In the NameSpace text box, enter \\server\root\cimv2 where server is the name of the server to which you want to connect.
4. Click Connect.
5. Click Query.
6. Enter select* from win32_process.
7. Click Apply.

...

1. Make sure that the Remote Procedure Call (RPC) service is running on the remote server.
2. Verify that there is a TCP listener on the remote server by running the netstat -nao command and verifying that there is the following entry: TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1304.
3. In the Tools subdirectory, run rpcping /s <servername> /t ncacn_ip_tcp where <servername> is the name of the remote server. This command verifies that RPC can communicate with the remote server and output similar to:
        Completed 1 calls in 15 ms
        66 T/S or 15.000 ms/T
4. Make sure that local or internal network firewalls do not block traffic by either disabling the firewall or configuring the Windows firewall to allow incoming RPC traffic.
5. Try to use the remote server IP address instead of the server name. If the IP address works, you may have a DNS issue.
6. If the remote server resides in a different domain, the two domains may not trust each other, or the user account does not have administrator permissions on the remote server/domain.
7. If both computers are in the same domain, and the user account has administrator permissions, try rejoining both computers to the domain.

Error: Access Denied

This error can indicate permission issues.

...

1. If the remote computer is running Windows XP, make sure it is not set to Force Guest. This setting forces impersonation of any connection as Guest.
   1. Open the Local Security Policy console from Administrative Tools.
   2. Browse to  Security Security Settings > Local Policies > Security Options.
   3. Double-click Network Access: Sharing And Security Model For LocalAccounts.
   4. Change the settings from Guest Only to Classic.
2. Make sure DCOM is enabled on the remote server:
   1. Run DcomCnfg DcomCnfg on the remote server.
   2. Click  Component Component Services.
   3. Expand Computers.
   4. Right click My Computer and select Properties.
   5. Click the Default Properties tabthe Default Properties tab.
   6. Make sure Enable Distributed COM on this computer is checked.
3. Verify the configuration of the correct DCOM remote launch and activation permissions:
   1. Run DcomCnfg on the remote server.
   2. Click Component Services.
   3. Expand Computers.
   4. Right click  My My Computer and select Properties.
   5. Make sure Enable Distributed COM on this computer is checked.
   6. Click the Com Security tabthe Com Security tab.
   7. Under Launch and Activation Permissions, click  Edit Edit Limits.
   8. In the Launch the Launch Permissions dialog boxdialog box, make sure your user account or group is listed in the Groups or user names list. If your user account or group is not listed, click Add and add it to the list.
   9. In the Launch Permission dialog the Launch Permission dialog box, select your user account or group in the Group or user names list. In the Allow column under Permissions for User, select Remote Launch and Remote Activation, and then click OK.
4. Make sure the correct DCOM remote access permissions are configured:
   1. Run DcomCnfg on the remote server.
   2. Click Component Services.
   3. Expand Computers.
   4. Right click My Computer and select Properties.
   5. Make sure Enable Distributed COM on this computer is computer is checked.
   6. Click the Com Security tabthe Com Security tab.
   7. Under Access Permissions, click Edit Limits.
   8. In the Access Permission dialog the Access Permission dialog box, select ANONYMOUS LOGON name in the Group or user names list. In the Allow column under Permissions for User, select Remote Access, and then click OK.
5. Make sure the correct WMI namespace permissions are configured.
   1. Run wmimgmt.msc.
   2. Right-click WMI Control, and then select Connect to another computer.
   3. Enter the remote server name, and then click OK.
   4. Right-click WMI Control, and then select Properties.
   5. In the Security tab, select the namespace, and then click Security.
   6. Locate the appropriate account, and then check Remote Enable in the Permissions list.

...