Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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 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 on the remote server.
    2. Click Component Services.
    3. Expand Computers.
    4. Right click My Computer and select Properties.
    5. Click the 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 Computer and select Properties.
    5. Make sure Enable Distributed COM on this computer is checked.
    6. Click the Com Security tab.
    7. Under Launch and Activation Permissions, click Edit Limits.
    8. In the Launch Permissions dialog 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 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 checked.
    6. Click the Com Security tab.
    7. Under Access Permissions , click Edit Limits.
    8. In 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. On the target machine, run wmimgmt.msc.
    2. Right-click WMI Control, and then select Properties.
    3. In the Security tab, select the CIMV2 namespace, and then click Security.
    4. Locate the appropriate account, and then check Remote Enable in the Permissions list.

 



Scroll pdf ignore
SQL 
SQLDiagnostic Manager
identifies and resolves SQL Server performance problems before they happen. Learn more > >

...

for SQL Server performance monitoring, alerting, and diagnostics for SQL Server.
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
|
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
|
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
|
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
|
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
|
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse

Save