I'm having an issue with Visual Studio Remote Debugging:
Machine 2: Windows 2007 > no domain > no firewall > Visual Studio Remote Debugging Monitor 64-bit 9.0.2122 (c) 2008 > Options... > No Authentication, Port=4015, allow any user to debug=true > OK > It says listening on 4015 in No Authentication Mode
Machine 1: Windows 2007 > no domain > no firewall > Visual Studio 2012 > DEBUG > Attach to Process > Transport = Remote(no authentication) > Attach to Machine2:4015 > Attach > It says:
Unable to connect to 'Machine2:4015'. Connection request was rejected by the remote debugger. Ensure that the remote debugger is running in 'No Authentication' Mode.
The remote debugger clearly says it's running in "No Authentication Mode".
What's the problem with VS2012 / MSVSMON?
What more does it want from me?!? :)
I had this same issue, but with VS2013. I couldn't connect with or without authentication. In my case it's C++ code but complicated by having two domains.
Turns out the remote tools are specific to the version and update level of Visual Studio:
You must install the update version of the Remote Tools for Visual Studio 2013 that matches the update version of your Visual Studio installation.
Once I updated to the correct msvsmon.exe I could connect to the remote PC.
in my case the message was
Ensure that the remote debugger is running in
'windows Authentication'
Mode.
its easy to add your Authentication, just fallow these steps..
tools
-> Options
windows authentication
then click
on permeation button
write everyone
then click Ckeck Names
then ok
thats it hope it help you,, and happy debugging!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With