Remote Debugging Failed After Windows XP SP2 Installed

I had a problem here, I installed the SP2 for Windows XP and I found that my
VS .Net 2003 cann't do remote debugging on my remote server (Windows Server
2003) anymore. I did setup all the needed configuration for my firewall as
instructed (open port TCP 135, UDP 4500 and UDP 500) but it still fail. I
even try to disable my firewall completely but I still ger the message sayin
g
: Can not start debugging, debugger component on server can not connect to
local machine.

If I uninstall SP2 from my Windows XP, everything will work fine. But once I
install put SP2 back in, I will get this error, anyone got any idea ?

This has been documented for months. See
http://msdn.microsoft.com/security/...remotedebug.asp


"SHSIOW" <SHSIOW@discussions.microsoft.com> wrote in message
news:2192812E-E60F-4355-85BE-65E2B2F7D960@microsoft.com...
>I had a problem here, I installed the SP2 for Windows XP and I found that
>my
> VS .Net 2003 cann't do remote debugging on my remote server (Windows
> Server
> 2003) anymore. I did setup all the needed configuration for my firewall as
> instructed (open port TCP 135, UDP 4500 and UDP 500) but it still fail. I
> even try to disable my firewall completely but I still ger the message
> saying
> : Can not start debugging, debugger component on server can not connect to
> local machine.
>
> If I uninstall SP2 from my Windows XP, everything will work fine. But once
> I
> install put SP2 back in, I will get this error, anyone got any idea ?

How I wish that document will solve my problem, but it doesn't :(

As I mentioned in my previous post, I did open all those port mentioned in
the document but it still don't work. I even disable the firewall completely
but it still give me the problem saying "The debugger component on server
failed to connect to local machine", once I remove SP2, everything will work
fine. I think my problem is not related to the document you mentioned, I
guess I am still missing something here.

"Ronny Ong" wrote:

> This has been documented for months. See
> http://msdn.microsoft.com/security/...remotedebug.asp
>
>
> "SHSIOW" <SHSIOW@discussions.microsoft.com> wrote in message
> news:2192812E-E60F-4355-85BE-65E2B2F7D960@microsoft.com... 
>
>
>

I think MDM service is somehow disabled on some system after SP2...

Goto VS.Net Debug group, you might find more info and solutions there.

"SHSIOW" <SHSIOW@discussions.microsoft.com> wrote in message
news:0F9B3780-DC67-4D39-B4EE-AE4339ED4F83@microsoft.com...
> How I wish that document will solve my problem, but it doesn't :(
>
> As I mentioned in my previous post, I did open all those port mentioned in
> the document but it still don't work. I even disable the firewall
> completely
> but it still give me the problem saying "The debugger component on server
> failed to connect to local machine", once I remove SP2, everything will
> work
> fine. I think my problem is not related to the document you mentioned, I
> guess I am still missing something here.
>
> "Ronny Ong" wrote:
> 

Did you read all the way to the bottom of the article? There are more steps
than just opening ports, and the firewall is not the only issue, so even if
you turn the firewall off, there are permissions that you may need to change
in NTFS and/or DCOM.


"SHSIOW" <SHSIOW@discussions.microsoft.com> wrote in message
news:0F9B3780-DC67-4D39-B4EE-AE4339ED4F83@microsoft.com...
> How I wish that document will solve my problem, but it doesn't :(
>
> As I mentioned in my previous post, I did open all those port mentioned in
> the document but it still don't work. I even disable the firewall
> completely
> but it still give me the problem saying "The debugger component on server
> failed to connect to local machine", once I remove SP2, everything will
> work
> fine. I think my problem is not related to the document you mentioned, I
> guess I am still missing something here.

Yep, I read all the way to the "rock bottom", the second part is for the
remote machine, my remote machine is on Windows 2003 Server, I don't think
there are any setting on that, right ? Just in case, I did also disable the
firewall setting n my server but it still don't work

"Ronny Ong" wrote:

> Did you read all the way to the bottom of the article? There are more step
s
> than just opening ports, and the firewall is not the only issue, so even i
f
> you turn the firewall off, there are permissions that you may need to chan
ge
> in NTFS and/or DCOM.
>
>
> "SHSIOW" <SHSIOW@discussions.microsoft.com> wrote in message
> news:0F9B3780-DC67-4D39-B4EE-AE4339ED4F83@microsoft.com... 
>
>
>