Thanks David... I want to Debug a ASP.NET WebApplication & WebService.
And what do you meen by "I always remote debug with the least
security"?
My user is in a domain and it has Administrative rights on both
machines, local and remote. When I start RDM on remote machine, I log
on with the user that I'm logged in on my local machine.
Thanks...
> Thanks David... I want to Debug a ASP.NET WebApplication & WebService.
>
> And what do you meen by "I always remote debug with the least
> security"?
I mean that the scenario that worked for you (with security disabled) is how
I normally remote debug. I don't try to get the security to work.
> My user is in a domain and it has Administrative rights on both
> machines, local and remote. When I start RDM on remote machine, I log
> on with the user that I'm logged in on my local machine.
Hmm, the article on using Windows Authentication said that should be all you
have to do... make sure you have an Admin account on the remote machine.
I'm not sure what else to try, sorry.
Good luck,
David
eusebiu - 25 Jun 2007 09:48 GMT
Hello...
I've was able to attach to aspnet_wp.exe on the remote machine like
this :
Remote Debugging Monitor
MSVSMON.exe : C:\Program Files\Microsoft Visual Studio 8\Common7\IDE
\Remote Debugger\x86
must be started on remote machine.
1. Administrative tools->Local security Policy-Local Policies-
>Security options
->Network access : Sharing and security model fol local accounts ->
Proprietes: Clients....(not guests) (both remote and local machine, if
the remote machine isn't a Windows 2K)
2. in msvsmon.exe, Tools->Options->Permissions->Add(the user name);
3. Start->Run->dcomcnfg->Component Services->Computers->My computer-
>Proprietes->
COM Security->Access Permisions->Edit limits-> Add the user to access
permotions and let him have remote access
4. the local user must have administrative rights on the the remote
machine as well;
(log in on remote machine with the same user that you are logged in on
the local machine)
Links: http://msdn2.microsoft.com/en-us/library/y7f5zaaa.aspx
Sometimes you should enable "Remote Access for Anonymous Logon"
MSDN : To enable Remote Access for Anonymous Logon
>From the Windows command prompt, run dcomcnfg:
C:\WINDOWS\System32\dcomcnfg
In the Component Services window, expand the Component Services/
Computers node.
Under Component Services/Computers, right-click on My Computer and
choose Properties from the shortcut menu.
In the My Computer Properties window, click the COM Security tab.
Under Access Permissions, click the Edit Limits button.
Select Anonymous Logon from the top list.
Select the Remote Access checkbox from the bottom list.
Click OK.
Click OK.
I hope this helps someone...