Share via

Error: Remote computer could not initiate DCOM communications 

  • Article

A DCOM error occurred when the remote machine tried to communicate with the local machine (the machine where you are running Visual Studio). This error may occur for several reasons:

  • The local machine has a firewall enabled.

  • Windows authentication from the remote machine to the local machine is not working.

  • You are remote debugging from a Windows XP SP2 machine with the Windows firewall enabled to a Windows 95/98/Me machine, and have not enabled Remote Access for Anonymous logon.

To correct this error

  1. If the local machine (the machine running Visual Studio) is running Windows XP Service Pack 2 and the Internet Connection Firewall is enabled, see How to: Set Up Remote Debugging for instructions on how to configure the firewall for local debugging.

  2. Test Windows authentication by trying to open a file share on the local machine from the remote server.

  3. To restore Windows authentication, try rebooting both machines. Check event logs on local and remote machines for Kerberos errors and check with domain administrators for known problems.

To enable Remote Access for Anonymous Logon

  1. From the Windows command prompt, run dcomcnfg:

    C:\WINDOWS\System32\dcomcnfg

  2. In the Component Services window, expand the Component Services/Computers node.

  3. Under Component Services/Computers, right-click on My Computer and choose Properties from the shortcut menu.

  4. In the My Computer Properties window, click the COM Security tab.

  5. Under Access Permissions, click the Edit Limits button.

  6. Select Anonymous Logon from the top list.

  7. Select the Remote Access checkbox from the bottom list.

  8. Click OK.

  9. Click OK.

See Also

Tasks

How to: Set Up Remote Debugging