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
'the de *** component on the server failed to connect to the local
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:
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
sure would be nice to hear from Microsoft on this...