STILL NOT ANSWERED, AGAIN: Remote Debugging, Windows XP

[Scott Swigart]

This is the third time I've posted this. Does anyone know the answer one
way or another?

----------------------------------------------------------------------

Has anyone been able to set up remote debugging between two XP machines that
are not part of a domain?

----------------------------------------------------------------------

I can't get remote debugging to work with Windows XP, and I wonder if it's
just impossible.

The machines are in workgroup mode, not part of a domain.

I have added a user called "Scott" to the Debugger Users group, and on the
remote machine, I have a user with the same name and password. (as far as I
know, you can't add a user on box1 to a group on box2 when they are in
workgroup
mode.).

If I attempt to open VS on one box, and attach to a process on another box,
I get:

Unable to connect to the machine. Access is denied. Verify that you are a
member of the 'Debugger Users' group on the machine that you are attempting
to debug.

So how can I add a user box1 to a group on box2 using XP in workgroup mode?

Thanks,
Scott

[Spider!]

i think i heard about this issue on remoting chat yesterday in msdn.see the
chat transcript . one host even provided a link to all remoting probs. i am
a stranger to this so please excusez moi !

----------------------------------------------------------------------------
---- Success is a bastard Every one claims to be its father Failure is an
orphan, No one wants it
Back from Death... To rule the World again ! Hell ! The Spider's Back !!!
"Scott Swigart" <sc...@3leaf.com> wrote in message
news:egXXSW6qBHA.2128@tkmsftngp07...

[Min Kwan Park[MSFT]]

I have some question about your problem.
- based on your post, you could see the process list on the remote machine
with "Processes" dlg, right?
- what type of debugging are you doing? native or managed(CLR) or Script?
- Is the process on the remote machine launched with "Scott" user account?
- Is "Scott" user account the member of "administrators" group?
the answer will be very appriciated for finding solution for you.

thanks
Min

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Scott Swigart" <sc...@3leaf.com> wrote in message
news:egXXSW6qBHA.2128@tkmsftngp07...

[Scott Swigart]

Answers in-line:

"Min Kwan Park[MSFT]" <mkp...@microsoft.com> wrote in message
news:OWQMN6qrBHA.1604@tkmsftngp04...

> I have some question about your problem.
> - based on your post, you could see the process list on the remote machine
> with "Processes" dlg, right?

No, I got the error as soon as I chose the remote machine in the Processes
dialog (Tools | Debug Process menu command)

> - what type of debugging are you doing? native or managed(CLR) or Script?

CLR

> - Is the process on the remote machine launched with "Scott" user account?

I'm attempting to debug an ASP.NET application. Everything on both boxes is
just a default install. I haven't changed the identity of the
aspnet_wp.exe.

> - Is "Scott" user account the member of "administrators" group?

Yes. The "Scott" account on both machines is a member of the administrators
group on each machine. But, these machines are part of a workgroup, not a
domain.

[Min Kwan Park[MSFT]]

Here is my suggestion.
On XP Pro, because of the default security setting for "sharing and security
model for local accounts", this remote debugging is not allowed by default.
Below is the steps to change this setting:
1. run "Local Security Settings" in Administrator tools.
2. select "Security settings\Local policies\Security options.
3. change "Network access : Sharing and Security model for local
accounts" from "Guest only - local users authenticate as Guest" to
"Classic - local users authenticate as themselves".
4. After this, need to reboot machine.
* this change should be applied onto the both machines for remote debugging.
After you make the setting change, you will be able to do remote debugging
with same name user accounts on both machines.

However, ***there is a concern with security with this change***. Because
you changed default setting of security model, it can expose:
- unexpected file sharing
- unexpected DCOM components sharing.
Before you make this change, any kind of connection from remote machine to
your machine was guaranteed as "Guest", but after this change, he/she could
be authenticated with your local user account. So, like the case of
Debugging, if you are sharing out a folder or DCOM object, there is a
possibility that any matched user(same user name and same password) on other
machine could access your shared objects.

I strongly recommend that, if you want to use this work-around, you need to
make sure that all user accounts have strong passwords, or you had better
setup network-Island for the debugging machines to prevent any malicious
attack.

thanks,
Min

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Scott Swigart" <sc...@3leaf.com> wrote in message

news:eQkI8S2rBHA.2280@tkmsftngp05...