XP SP2 and Remote Debugging

XP SP2 and Remote Debugging

Post by phil_beise » Thu, 12 Aug 2004 00:00:38


I just installed Windows XP SP2 and I can no longer remote de ***
programs.

I followed all the instructions regarding firewall configuration
(allowing specific ports, etc.) and even tried turning off the
firewall all together.

The error I get when attempting to list the processes on a remote
machine is "Access is Denied".

This is VS.NET 2003 with the just released version of XP SP2.
 
 
 

XP SP2 and Remote Debugging

Post by michael.fo » Thu, 12 Aug 2004 15:36:45


See this discussion:

http://www.yqcomputer.com/ %4040tude.net&prev=/groups%3Fhl%3Den%26lr%3Dlang_en%26ie%3DUTF-8%26group%3Dmicrosoft.public.vsnet.debugging

or do a groups search for 'WinXP SP2 disables debugging (MDM.exe)'

 
 
 

XP SP2 and Remote Debugging

Post by phil_beise » Fri, 13 Aug 2004 00:16:08

I looked at that discussion. I fail to see any remedy there.
 
 
 

XP SP2 and Remote Debugging

Post by RnJFYUtfQE » Mon, 16 Aug 2004 18:13:01

I have the same problem too.

I've posted the problem also on the asp.net forum and received a message...

http://www.yqcomputer.com/
 
 
 

XP SP2 and Remote Debugging

Post by phil_beise » Wed, 18 Aug 2004 09:35:28

This may have something to do with the fact that the remote machine is
Windows 2003. Any ideas?
 
 
 

XP SP2 and Remote Debugging

Post by Sorin Sand » Wed, 18 Aug 2004 13:58:56

If anyone find's out a solution for this problem or find an update or patch
at Microsoft please post here.
 
 
 

XP SP2 and Remote Debugging

Post by Christoph » Wed, 18 Aug 2004 14:18:26

This article mentions Remote DCOM Debugging as a possible problem with
Visual Studio and XP SP2:
http://www.yqcomputer.com/
--
http://www.yqcomputer.com/
 
 
 

XP SP2 and Remote Debugging

Post by RnJFYUtfQE » Wed, 18 Aug 2004 21:15:03

I've found a workaround at codinghorror.com that is working...

August 12, 2004

DCOM, XP SP2, and Remote Debugging
I debug remotely at home, mostly because I prefer not using the crippleware
version of IIS. It's kind of a pain to get it running, because you have to be
more careful with permissons and configuration, but basically it works. At
least, it worked until I installed XP SP2, anyway. There's a decent set of
documentation on how to get Remote Debugging working under SP2, but I could
not get it to work-- and I have the XP firewall completely disabled! Over and
over, any attempt to remotely debug an ASP.NET app resulted in this exciting
dialog box message:
Error while trying to run project: Unable to start debugging on the web
server. Access is denied.
I ran through all the usual troubleshooting, and then some:
I have the same account/password on both client and server
the website is using NTLM authentication
there is an IIS application for the website
I am a member of the Administrators and De *** Users group on both boxes.
the website loads fine if I run with CTRL+F5, eg, no de ***
The security event log shows me logging in just fine on the server
Remote Debugging support is properly installed on the server
After three hours of intense frustration, I started to feel like that Doom3
zombie-- the one mindlessly pounding his head against a *** y wall over and
over. Eventually you get to that desperate point where you'll try anything,
no matter how crazy. Sometimes this pays off, and sometimes it doesn't.
Luckily this is one of those times where the headbanging paid off. I finally
got remote debugging to work with XP SP2 by granting "Remote Access" to the
ANONYMOUS LOGON account in dcomcnfg.exe on the client computer. Specifically,
in
dcomcnfg.exe -> Component Services -> Computers -> My Computer -> Properties
-> COM Security -> Access Permissions -> Edit Limits.
Now, the documentation does mention setting stuff in Edit Limits, but it
says you have to add your account in there, and only if you're not an
administrator. That doesn't even make sense; out of the box EVERYONE is
granted both local and remote permissions in Edit Limits. Granting remote
access to ANONYMOUS LOGON is what you have to do. Why, I have no idea, but it
is totally repeatable across three computers here, including my otherwise
unmodified laptop. There are plenty of people in google groups complaining
about this problem, so hopefully this will help someone.
Oh, and by the way, be careful: this is also a great way to trash your
machine. I strongly suggest you only grant additional permissions in
dcomcnfg; do not remove any permissions. In the process of testing this--
ironically, after I finally got it working, and in order to ensure that I
understood the failure conditions-- I inadvertently removed all permissions
from the Edit Limits box. Friends, do not do this. Two in-place reinstalls
later (one reinstall to get COM permissions back, another one to re-install
the COM stuff that failed to install with the borked permissions), I had a
functioning OS again. Revenge of COM...
 
 
 

XP SP2 and Remote Debugging

Post by RnJFYUtfQE » Wed, 18 Aug 2004 21:27:02

I've found a workaround at codinghorror.com that is working...

August 12, 2004

DCOM, XP SP2, and Remote Debugging
I debug remotely at home, mostly because I prefer not using the crippleware
version of IIS. It's kind of a pain to get it running, because you have to be
more careful with permissons and configuration, but basically it works. At
least, it worked until I installed XP SP2, anyway. There's a decent set of
documentation on how to get Remote Debugging working under SP2, but I could
not get it to work-- and I have the XP firewall completely disabled! Over and
over, any attempt to remotely debug an ASP.NET app resulted in this exciting
dialog box message:
Error while trying to run project: Unable to start debugging on the web
server. Access is denied.
I ran through all the usual troubleshooting, and then some:
I have the same account/password on both client and server
the website is using NTLM authentication
there is an IIS application for the website
I am a member of the Administrators and De *** Users group on both boxes.
the website loads fine if I run with CTRL+F5, eg, no de ***
The security event log shows me logging in just fine on the server
Remote Debugging support is properly installed on the server
After three hours of intense frustration, I started to feel like that Doom3
zombie-- the one mindlessly pounding his head against a *** y wall over and
over. Eventually you get to that desperate point where you'll try anything,
no matter how crazy. Sometimes this pays off, and sometimes it doesn't.
Luckily this is one of those times where the headbanging paid off. I finally
got remote debugging to work with XP SP2 by granting "Remote Access" to the
ANONYMOUS LOGON account in dcomcnfg.exe on the client computer. Specifically,
in
dcomcnfg.exe -> Component Services -> Computers -> My Computer -> Properties
-> COM Security -> Access Permissions -> Edit Limits.
Now, the documentation does mention setting stuff in Edit Limits, but it
says you have to add your account in there, and only if you're not an
administrator. That doesn't even make sense; out of the box EVERYONE is
granted both local and remote permissions in Edit Limits. Granting remote
access to ANONYMOUS LOGON is what you have to do. Why, I have no idea, but it
is totally repeatable across three computers here, including my otherwise
unmodified laptop. There are plenty of people in google groups complaining
about this problem, so hopefully this will help someone.
Oh, and by the way, be careful: this is also a great way to trash your
machine. I strongly suggest you only grant additional permissions in
dcomcnfg; do not remove any permissions. In the process of testing this--
ironically, after I finally got it working, and in order to ensure that I
understood the failure conditions-- I inadvertently removed all permissions
from the Edit Limits box. Friends, do not do this. Two in-place reinstalls
later (one reinstall to get COM permissions back, another one to re-install
the COM stuff that failed to install with the borked permissions), I had a
functioning OS again. Revenge of COM...
 
 
 

XP SP2 and Remote Debugging

Post by kf » Thu, 19 Aug 2004 00:58:51

Hello,

I want to post some additional info I came up with when resolving this problem. I changed the anonymous permission as mentioned above but then got another error. Something about not having enough storage space. I turned failure audit logging on the client and server and found that VS uses NTLM authentication. I had to go to the server in Local security policy, set the LAN Manager Authentication level to Send LM & NTLM and NTLMv2 if negotiated. Then I found that I had to go to the XP client and set this same setting to respond to NTLM v2. I have my theories about this but it doesn't make sense as to why you'd have to do. I called MS to report it and the person on the other end didn't have these settings but they weren't using XP SP 2.

Good luck.



**********************************************************************
Sent via Fuzzy Software @ http://www.yqcomputer.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
 
 
 

XP SP2 and Remote Debugging

Post by phil_beise » Thu, 19 Aug 2004 02:30:18

I will give that a try. Why oh why can't Microsoft speak up about this?
 
 
 

XP SP2 and Remote Debugging

Post by phil_beise » Thu, 19 Aug 2004 04:18:16

ok, i got remote debugging working...

I needed to do a couple of things:

0. ran the "De *** FirewallConfiguration.EXE" tool available from
microsoft, which i think just opens the various ports in the firewall.

1. follow the instructions in the codinghorror.com posting

this got me past the "access is denied" error, but then i encountered
this:

'the de *** component on the server failed to connect to the local
machine'

2. with the error message above, i clicked the help button and
followed the instuctions there (this has you changing the "network
access: sharing and security model for local accounts") setting.

that didn't quite work (but i didn't undo it), i then found this:

3. follow the instructions here:

http://www.yqcomputer.com/ *** +component+failed+to+connect+to+the+local+machine&hl=en&lr=&ie=UTF-8&safe=off&selm=ae5b757d.0305170849.33f362d8%40posting.google.com&rnum=5

the instructions here talk about giving specific permission to
Administrator and De *** Users, i gave specific permission to the
user I am logged in as, which amounts to the same thing...

in any event, these instructions talk specifically about the Microsoft
CLR De *** , which covers my case...

so i think I am home free, although I couldn't explain it to others on
a bet. In fact, I am going to print out this very posting so I can
remember what I did. No wonder COM/DCOM is such a nightmare for
everyone; I, for one, am glad to have moved into the .NET world and
only occasionally have to make friends with COM/DCOM (as in this
instance).

sure would be nice to hear from Microsoft on this...
 
 
 

XP SP2 and Remote Debugging

Post by Floris Bri » Thu, 19 Aug 2004 16:43:15

This solution worked for me, I was just trying everything yesterday so that
gave other errors. This morning I also tried it on a "clean/freshly sp2"
installed pc of a colleague and also he is working without any problems.



Security and usability won't go hand in hand.
 
 
 

XP SP2 and Remote Debugging

Post by phil_beise » Fri, 20 Aug 2004 14:38:22

I did not restart; so maybe the other steps were not necessary had I
restarted. this I don't know. thanks for everyone's help.
 
 
 

XP SP2 and Remote Debugging

Post by S2lwbGluZ » Fri, 27 Aug 2004 14:19:09

I wanted to add a note here as well. The step:
dcomcnfg.exe -> Component Services -> Computers -> My Computer -> Properties
-> COM Security -> Access Permissions -> Edit Limits

helped me as well, but I didn't add remote access to the anonymous user.
Instead I added Authenticated users and gave them remote access, and that
worked for me.