Visual Studio 2005 Remote Debugging

Question

<!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:595.3pt 841.9pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:35.4pt; mso-footer-margin:35.4pt; mso-paper-source:0;} div.Section1 {page:Section1;} -->

Hi guys

I've been searching the web and couldn't come up with a solid solution.

I've been trying to remote debug an application running on a remote PC running Windows XP with SP 2. No I've tried about a million things to attach to a process from my computer on this remote PC. I can access the shared files and I've even disabled the firewall and set specific exceptions in the firewall settings.  I've set up the DCOM components and even build the application directly to the remote PC.

The main issue lies where I want the breakpoints to hit on my VS 2005 IDE where the source code is. The reason that I'm stating the obvious is so that I don't leave anything out. Here's the full fact.

I can't attach to the server created by the Remote debugger running on the remote PC. This PC does have VS 2005 running on it as well, so the debugger has been installed successfully. The error message created by my VS is the following:

Unable to connect to the Microsoft visual studio remote Debugging Monitor named "name@remotepcname". The System detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.

 

Now first of all, I don’t know how to make sure I can contact that server which authenticated me.

 

Does anyone know how I can fix this. Please

 

Thank you

Answer 1

Hello,

To trouble shoot the issue, would you please tell us which mode did we choose, Windows Authentication mode or No Authentication mode?

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework!

Answer 2

Hi. I tried it with No Authentication first, this works, but I cant seem to get the syblos to load for the break points in my code to hit. The No athentication mode is for native code only, so this is why I switched to Windows Authentication mode, to see if the symbols will load and the break point will be hit, and then I struck this WALL!!!!!

So the selected mode which gives me this issue is Windows Authentication mode.

Answer 3

Hello,

To make Visual Studio to load the symbols, one of the ways is to make a shared folder and add its path to the environment variable named _NT_SYMBOL_PATH on the remote server which is running the Remote debug monitor.

By the way, what code do we want to debug? is it managed code or native code? No Authentication mode only supports native debugging. If we switch to Windows Authentication mode, higher security level is used. Hence, there are more configuration we need to configure, for example, firewall issue and user's permission. Please refer to this KB article for detailed information on how to Implement Remote debugging in Visual Studio 2005:
http://support.microsoft.com/kb/910448

Best regards,

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework!

Answer 4

Hello

We're looking at debugging managed code. That's why we are trying the windows authentication mode.

The symbols which should be loaded are located in the directory of the application files. This is what worries me, why would they not be loaded. The loading scheme works by reverting to the application's current directory and then to the Windows directory as far as I know, but I will try what you suggested above.

Thank you.

Answer 5

Hello Bramenator,

Please take it easy, I'll help you with this issue. When we remote debugging, Visual Studio Debugger will look for  the pdb files from the remote machine and seek the source code on our local machine. If we did not specify where the debugger could find the pdb file, then, the symbols could not be loaded. In this case, since we put our symbol files on the directory of the application, hence, the remote debugger monitor running on the remote machine could not find this location for the pdb files. One of the ways to let it know where to find the symbols is, as I suggested above, we could make a share folder on the local machine and add its path to the environment variable on the remote machine to let the remote debugger know where to find the symbols.

Please take a look at this video on remote debugging with MSVSMON.exe, I believe it could help you:
http://www.microsoft.com/uk/msdn/screencasts/screencast/313/Visual-Studio-2008-Remote-Debugging-with-MSVSMONEXE.aspx

Best regards,

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework!