Error: The Visual Studio Remote Debugger service on the target computer cannot connect back to this computer

Error: The Visual Studio Remote Deb...

Collapse All

This page is specific to

Microsoft Visual Studio 2010/.NET Framework 4

Other versions are also available for the following:

Visual Studio Debugger

Error: The Visual Studio Remote Debugger service on the target computer cannot connect back to this computer

This error means that the Visual Studio Remote Debugger service is running under a user account that cannot authenticate when it tries to connect to the computer that you are debugging from.

The following table shows what accounts can access the computer:

	LocalSystem account	Domain account	Local accounts that have the same username and password on both computers
Both computers on the same domain	Yes	Yes	Yes
Both computers on domains that have two-way trust	No	No	Yes
One or both computers on a workgroup	No	No	Yes
Computers on different domains	No	No	Yes

In addition:

The account you run the Visual Studio Remote Debugger service under should be an administrator on the remote computer so that it can debug any process.
The account also has to be granted the Log on as a service privilege on the remote computer that is using the Local Security Policy administrative tool.
If you are using a local account access the computer, you must run the Visual Studio Remote Debugger service under a local account.

To correct this error

Make sure the Visual Studio Remote Debugger service is correctly set up on the remote computer. For more information, see How to: Set Up Remote Debugging.
Run the remote debugger service under an account that can access the debugger host computer, as shown in the previous table.

To add "Log on as a service" privilege

On the Start menu, choose Control Panel.
In Control Panel, choose Classic View, if necessary.
Double-click Administrative Tools.
In the Administrative Tools window, double-click Local Security Policy.
In the Local Security Settings window, expand the Local Policies folder.
Click User Rights Assignment.
In the Policy column, double-click Log on as a service to view current local Group Policy assignments in the Log on as a service dialog box.
To add new users, click the Add User or Group button.
When you are finished adding users, click OK.

To work around this error

Run the Remote Debugging Monitor as an application instead of a service.

Tasks

Remote Debugging Errors and Troubleshooting

Other Resources

Remote Debugging Setup

Tags

: Add a tag

Community Content

Add new content

Annotations

Use RunAs to resolve this problem when running as an application

Eric Loveland ... Thomas Lee | Edit | Show History

If you're running the Remote Debugger Monitor on the remote computer as an application and you still get this error, you can resolve the problem by using RunAs to launch the msvsmon.exe on the remote machine as a user that has access to the local machine (you can use a domain user if you do DOMAIN\USERNAME):

C:\Windows\System32\runas.exe /noprofile /netonly /user:{USER_WITH_ACCESS_TO_LOCAL_MACHINE} msvsmon.exe

Tags

: Add a tag

Flag as ContentBug

I had to enable DCOM?

Johan Vervloet | Edit | Show History

I had this situation:

domain A and domain B, B is trusted by A.
application is running on domain A, and being developed on domain B
remote debugging monitor runs on domain A, as user of domain B, which is domain admin in domain A

This worked, until today. (Or some days ago, I didn't test it recently.)
I tried a lot of things:

fiddling with the firewall
using local user for debugging monitor
moving development machine to domain A, or to a workgroup

Nothing worked.

Eventually, I found this: http://stackoverflow.com/questions/4923400/configure-visual-studio-2010-remote-debugger/7436941#7436941 which suggested to enable dcom on my development machine. DCOM wasn't enabled indeed, I re-enabled DCOM, and now it works again.

Now I am not sure what went wrong. Did something turn DCOM off? Did something changed such that DCOM is required now, and wasn't before. Is this DCOM thing irrelevant, and was it just a temporary failure of one of our domain controllers? I don't know.

Tags

: Add a tag

Flag as ContentBug

Debugging with unavailable domain controller

Anlo2846 | Edit | Show History

I've had a lot of trouble getting remote debugging across domains to work. My development laptop belongs the A domain and the remote computer to the B domain. They do not have two way trust and the domain controller of domain A is not available from the site of the remote computer. I tried setting up local accounts according to this article, but still got the authentication failed message. The only way I got it to work is by making my laptop leave the A domain.

Tags

: Add a tag

Flag as ContentBug