remote debugger over internet

visual-studio-2010 remote-debugging
Samarth Bharadwaj picture Samarth Bharadwaj · Jun 23, 2011 · Viewed 8.8k times · Source

my setup is as flows: Local development PC: x86 vista with visual studio Client server: x64 server 2008 r2 with static ip and internet.

Currently I connect with it using Remote desktop. Can i configure remote debugger to this setup? if so, how? what must i fill in qualifier field in attach process window.

remote debugger is running as service and there is a user name with login as service privilege.

guides, experiences will make my life little less of a hell. Thanks.

Answer

Robert Hyatt picture Robert Hyatt · Apr 29, 2013

I had a similar problem, and like Hans Passant said above, a VPN is necessary. I was able to attach to the process and debug over the internet by doing the following:

  1. Install the latest microsoft remote debugger on the server.
  2. Install Hamachi on both my local machine and the server and connect so that I was on the same network.
  3. Go to Debug->Attach To Process on my local machine's Visual studios and enter the Hamachi IP address of the server.
  4. Pick "show processes from all users" and pick the process in question.

Note: I was logged in as the exact same user on both machines and had the same password on each.

I hope that helps someone out there.

Related questions

How to set up remote debugging on a machine without Visual Studio

Is there a way to set up Remote Debugging (Msvscom.exe) on a machine that does not have Visual Studio installed? I would like to attach to the service running on the VM so I can debug an issue in …

Read More
Configure Visual Studio 2010 Remote Debugger

I have installed the Visual Studio 2010 Remote Debugger on a Windows Server 2003 (x86) server, and am attempting to connect to it results in the following error: Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'ServerName'. The …

Read More
Visual Studio remote debugger "invalid access to memory location" feature

This is another attempt to resolve the problem stated here. Unfortunately the topic was closed without adequate resolution found, as apparently the original poster had issues with symbols, not with visual studio problem itself. Problem Statement: Visual Studio 2012 (and 2010 for …

Read More