Paul Fallon's WebLog

From Ireland: a little bit of this and a little bit of that

XP SP2 and Remote Debugging

With the security enchancements in XP SP2, Remote Debugging will be disabled. To Enable remote debugging you need to follow the steps outlined here.
Published Sunday, August 08, 2004 8:24 PM by no1138
Filed under:

Comments

 

Kevin Lo said:

What if the ICF is disabled? Remote Debugging STILL doesn't work. Unfortunately uninstalling SP2 is the only solution at the moment.
August 16, 2004 2:48 PM
 

Paul said:

Hi Kevin,
one possibility might be the priviliges of the account you are using? are you an admin on the remote machine?

thx,
P.
August 16, 2004 3:00 PM
 

Kevin Lo said:

Sure am! I'm an admin and in the remote debugging group. I'm on an XP machine trying to remotely debug a .net service on a Windows 2003 server. I've tried reconfiguring dcom's permissions as well-- no such luck. Installing SP2 on a fresh XP install causes remote debugging to fail. Uninstalling it, remote debugging works again. The microsoft.public.vsnet.debugging newsgroup has many others who are experiencing this same thing.
August 16, 2004 3:22 PM
 

Peter Kron said:

It also seems to be affecting localhost debugging of ASP. NET apps.The steps you outline seem out of date with the current UI. Is it just port 135 that is critical?
August 17, 2004 5:48 AM
 

pb said:

hi kevin,
i wonder if the remote machine in your scenario is a Windows 2003 box? this is my configuration (meaning the client is XP SP2 and remote machine Windows Server 2003) and it fails regardless of how my ICF is configured or even if it is turned OFF.
August 17, 2004 1:32 PM
 

Floris Briolas said:

Well it's clear to me, more security won't go hand in hand with usability. Also the screenshots used in the msdn article are different on my computer, but it's workable. Haven't got it to work do.
Have you, Paul Fallon, managed to get things going?
August 17, 2004 1:39 PM
 

Kevin Lo said:

I found the solution from a vsnet.debugging newsgroup post. Grant "Remote Access" permissions 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.
August 17, 2004 7:53 PM
 

Floris Briolas said:

I would like to confirm the ANONYMOUS LOGON solution. It works (loud yahoo) found it on my own do,.. but it gave me other errors, so I hesitated if this was the right solution. On my way home I realized I most likely made a mistake in the settings of vs.net / build and debugging. SP2 doesn’t seem so bad after all.
August 18, 2004 8:30 AM
 

Anthony Nedolast said:

I have been looking for this solution for the past hour... Allowing access to anonymous logon solved my problem!
August 21, 2004 7:53 AM
Anonymous comments are disabled

This Blog

Syndication

News

The content of this site are my own personal opinions and are not intended to represent my employer's view. In addition, my thoughts and opinions may change over time, so out of date posts do not necessarily reflect my current thoughts and opinions. These postings are provided "AS IS" with no warranties, and confer no rights.


BlogJet 
Subscribe in NewsGator Online 
Add to My Yahoo!
Add to My MSN

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker