visual studio .net debugging: Hi all,
I want to use the remote debugging from VS 2005 that exists in my XP Pro SP2
machine
the remote machine is Windows server 2003
I got the error:
Logon failure: unknown user name or bad password
then I follow the instructions that exists in:
http://msdn2.microsoft.com/en-us/library/ek2256kk.aspx

BUT
I cannot add the user of the XP machine , only the machine itslef , when I
click the Add User or Group button and change the location from "myserver"
to "myworkgroup" , I can find my xp machine , vut I can't find USERS on this
machine.
when click the Objects Types button I only have "computers" , the "users" ,
"groups" and "built in security principals" object typesare not exists.
someone know how to solve it ?
Thanks

Hi Semedao,

Based on my understanding, you want to setup remote debugging between 2
workgroup machines.

Have you setup a local account with the same name and password on remote
Win2003 machine as your WinXP machine? This is a must while debugging
between 2 workgrounp machines.

Regarding remote debugging, the local debugger's debugging request to the
remote machine must be authenticated, and then mapped to an identified
known account on the remote machine.

In domain environment, this is easy to complete, you can just use a domain
account on local machine for cross-machine debugging, once the remote
machine has added this domain account to debug account, everything will be
OK.

In workgroup scenario, your local WinXP machine's account(let's call it
*Alice*) is only known to this local machine. All of *Alice*'s
information(such as password) is stored in WinXP machine. The remote
Win2003 machine has no knowledge about who is *Alice*. Without domain, the
Win2003 machine can not also contact the DC to help authenticate the
*Alice*, so the remote debugging will fail.(The Win2003 machine can not
recognize *Alice*, so he can not trust a stranger's debugging requst). This
is why you can not find *Alice* account on WinXP.

To resolve this problem, the most common solution is setup a new account on
Win2003 machine with the same account name and password. Then Win2003
machine has the enough information to identify the request is coming from
*Alice*. This is confirmed in the "One or both computers on a workgroup"
row in the link below:
http://msdn2.microsoft.com/en-us/library/ms164725.aspx

Above is the principle. After setting up an account, you should look up the
new created *Alice* account on Win2003 machine instead of *Alice* account
on WinXP machine, since the remote debugging request will map to this local
*Alice* account. Then you may assign permission and LSA setting to this
local *Alice* account on Win2003.

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Semedao,

Have you reviewed my reply? Does it make sense to you? Please feel free to
tell me, thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi , sorry that I forgot to response
I saw it , and it's work (strange , but only fater couple of reboots etc..
sudenly it start to work)
but then....
I start to get some SecurityPermission exceptions (I have my own server in
the remote machine that listen etc)
in this stage I realized that I am waisting time on something that only
should help me short the development time and in fact... make it the
opossite... :)
so I install VS also on hte remote machine...
in any case , thanks for the good response
and... If you can tell to the people there (MS) that I think that
developers.. still want to be developers , not system administrators , the
debug (and other issues also with VS) should be one click and - use it
they must think about make all those issues more simlpe and fast.
thanks again
[quoted text, click to view]

Hi Semedao,

Thanks for your feedback!

Yes, I understand your concern. Remote debugging is somewhat hard to
configure than local debugging. However, this is due to security issue.
Debugging requires high level controlling of the debuggee process. In
remote debugging scenario, it means that the debugger on machineA can
control the debuggee process on machineB, and the debugger can access all
the memory of the debuggee process on machineB. This is really a high
priviledge, which should only give to good guys.

Windows is a secure operation system, it does not allow bad guy to take
control of your machine easily, so it will give the remote debugging
priviledge to whom he trusts. To identify the good guy from bad guy,
Windows uses authentication to recognize good guy and refuses bad guy. By
doing remote debugging between 2 machines without in the same domain, the
authentication between them is even harder, so there may be some strange
problems in the cross-machine authentication.

Anyway, I will help to forward your concern to our VS debugger team. Also,
it is a good chance for you to report this issue to our product team from
our formal feedback center below:
"Visual Studio and .NET Framework Feedback"
http://connect.microsoft.com/feedback/default.aspx?SiteID=210

This will help to increase the issue priority.

Again thanks for your understanding.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.