Re: problems remote debugging using VS 2005
- From: "Yamin" <yaminb@xxxxxxxxx>
- Date: 13 Oct 2006 18:57:21 -0700
vdoddy@xxxxxxxxx wrote:
we are having problems using the VS2005 debugger. we're using the
remote debugging where the process is running on a remote machine.
we're using the following settings in the properties tab:
Remote Server Name= IP where the process to be debugged is running
Connection = Remote with no authentication
Debugger type=Native only
But it looks like msvsmon.exe that is running on the remote machine
needs a lot of ports to be open. it looks like it opens random ports in
the range from 1000-2500. But we don't want to open all those ports
because of security issues. Is there any way that we can open only few
ports like (may be upto 5 ports or so) ?
Do we need to use "Connection=Remote with windows authentication"? If
so, is there any document that explains how to do this. Also do we need
to have the remote machine and the PC from which you are debugging to
be in the same domain?
Thanks
I got my vs 2005 working with remote debugging.
I had to put them in the same domain.
I had to add the local machines user name to the remote's debug access
permissions.
I use it with remote with windows authentication, but sometimes after
reboots or what not, it doesn't like it so I which to remote with no
authentication :)
Also, on the local, in the local security policy, there is an option (I
can't remember the exact name, but its like Access to remote shares
"classic or log on as guest". Change that to classic (log on with
username)
And all the switches it says for the msvsmon.exe just don't work. When
I try them, it just says the switch is invalid. Go figure.
But once you get past the security permissions, it debugs flawlessly.
It's weird to say the least. Wish it was as simple as the VS 6.0
remote debugger :)
.
- References:
- problems remote debugging using VS 2005
- From: vdoddy
- problems remote debugging using VS 2005
- Prev by Date: Javascript debugging
- Next by Date: Re: Conditional Break
- Previous by thread: problems remote debugging using VS 2005
- Next by thread: Debug from unmanged C++ to managed C++
- Index(es):
Relevant Pages
|
