VS 2008 Remote debugger error: "remote debugger cannot connect back" RRS feed

  • Question

  • I am having a hopeless time trying to setup remote debugging between two machines. The error I keep getting is this:

    "Unable to start debugging on the web server. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. A firewall may be preventing communication via DCOM to the local computer".

    Here is my configuration:

    Dev machine: windows XP SP2
    Remote test machine: Windows server 2008

    Both are part of workgroup on the same subnetwork behind a firewall.

    I have read several articles on the subject and have done the following:

    1. Each machine is using an account with administrator privliges (i.e. i am logged into both with this account on each).
    2. This account has the same username and password on both machines
    3. Due to exceptions in win XP, (as per several articles' instructions) I have altered the sharing and security model for local accounts to "classic" as well as enabled anonymous access for DCOM via the Dcomcnfg.exe configuration applet.

    Both steps are outlined here: 


    and here:


    Further, I have followed all the steps in this article:


    which deals with, among many others steps, debugging a remote iis 7.0 asp.net site from VS 2008 using machine that are part of a workgroup.

    Further, I have verified that both machines are visible to each other on the local network. I have successfully created and accessed shares on each machine bidirectionally.

    I have started the remote debugger on the remote machine in application mode, and verified that the dev machine is able to connect to it (this connection shows up in the msvsmon status window). The problem, apparently, is the connection back from the server to the dev machine.

    Last thing is that I was able to connect by shutting off all authentication in msvsmon on the server and changing the transport to "Remote (native only with no authentication)". I was able to connect and see processes on the server, however, this is useless as I need to debug an asp.net site, not native code.

    Any ideas? I have literally been all over MSDN and have found no other info on this. Any help would be hugely appreciated.

    Thursday, March 26, 2009 10:06 PM


  • Hi, did you try execute visual studio with: run as... > and dont put machine\adminsitrator , put (MACHINE-DEBUGGER-DOMAIN)\Administrator
    Friday, August 21, 2009 11:18 AM