Visual Studio 2005 cannot "Attach to Process" for IIS for remote debugging
Posted on 2009-05-05
I am trying to perform remote debugging using Visual Studio 2005.
Visual Studio Remote Debugging Monitor starts successfully on the remote computer (the one with IIS). I run it remotely from my local computer.
It gives me a server name which I assume is a virtual server of the form DOMAINNAME\username@LOCALCOMPUTERNAME.
In Visual Studio, I load my classic ASP file, the click on Debug - Attach To Process.
I enter the above virtual server name as qualifier. I make sure both "Show processes for all users" and "Show processes in all sessions" are checked.
All of the instructions I have found at MSDN and other places tell me that I should be able to select w3wp.exe (the IIS 6 process on the remote server) and then perform debugging.
Unfortunately, the w3wp.exe process is not listed. In fact, the processes listed appear to be the ones on my LOCAL computer.
Can someone tell me why I am not seeing the necessary process?
I have administrative permissions on both machines and am in the group "debugger users". There is no firewall between the machines.
(An attempt to use the Remote Debugger Configuration Wizard to "run as service" resulted in successful configuration but failed due to invalid logon, so I am trying to make the manual connection work.)