2

Hey everyone, I'm having trouble configuring my remote debugging set up. I've been searching and reading for a while, but I can't figure it out. I'm running windows 7 as the pc I'm running VS on and then have windows 7 running in virtual box as the pc that is running the program I'm trying to debug. I'm trying to debug a .NET 4 project.

Both computers are not part of a domain (I'm not sure if that matters). I'm running the debug monitor on the virtual pc via a shared folder on the non-virtual pc.

When I try to connect to the remote pc in the attach to process window in VS it connects, but fails to launch, and I get an error that says 

Error while trying to run project: Unable to start debugging.
The specified network name is no longer available.

Let me know if I need to say anything else about my set-up.

Thanks for the help!

Improve this question
8
  • 1
    Have you verified that there are no firewalls blocking the remote debugging ports? If using Windows Firewall then add Visual Studio to the exception list.
    – maple_shaft
    Commented May 10, 2011 at 14:21
  • I haven't touched the firewall other than the changes windows makes when running the debug monitor.
    – wangburger
    Commented May 10, 2011 at 14:25
  • 1
    I never trusted when Windows would "help you out" by opening up the ports like that. It is always best to double check that an exception was created for Visual Studio on your server machine. You mentioned it wasn't on a domain but if both machines are connected to the same router then it is possible that the router firewall could be blocking these ports as well. Barring a firewall issue, you must ensure that the application assemblies hosted on the server have been built in Debug mode and NOT Release mode. Release mode is trimmed down and doesn't contain debug symbols.
    – maple_shaft
    Commented May 10, 2011 at 14:29
  • It turned out I didn't have the firewall setup correctly, but I disabled the windows firewall for each machine and then tried again, but it still didn't work. It's still giving the same access denied error.
    – wangburger
    Commented May 10, 2011 at 14:51
  • And the router firewall if applicable? Did you confirm that the application was built in Debug mode?
    – maple_shaft
    Commented May 10, 2011 at 14:59

1 Answer 1

Reset to default
3

I finally figured out my problem(s).

  1. I was using the wrong PC name to connect to the host machine. I was using the Server name that you can type in the VS remote debugging monitor. I had it working when I did the server as '[email protected]...' where that was the actual ip address on my subnet

  2. Windows didn't properly configure the firewall ports for me. I had to manually open the DCOM ports to get it connecting.

  3. I had to clear the existing credentials for each machine once everything else was set up as is shown here http://msdn.microsoft.com/en-us/library/2dbesfyx.aspx

Thanks everyone for your help and pointers.

Improve this answer
1
  • #1 helped me - I was also using the server name
    – J Cooper
    Commented Sep 25, 2012 at 20:18

Not the answer you're looking for? Browse other questions tagged or ask your own question.