I am trying to set up remote debugging from my development machine into a production environment running in a virtual machine, but no matter what I do I get the following error:
Unable to connect to the Microsoft
Visual Studio Remote Debugging Monitor
named . The
Visual Studio Remote Debugger on the
target computer cannot connect back to
this computer. Authentication failed.
Please see Help for assistance.
This is my setup:
Host Machine:
Windows 7 Professional x86
Visual Studio 2010 Ultimate
Virtual Machine:
Windows 7 Professional x86
Both computers are on the same domain, with the same username and password. The firewall on the remote computer is turned off and the firewall on the host is on, but turning it off produces the same error. The accounts on both machines are members of the Administrators group and running both msvsmon and visual studio as administrator or either/or produces the same result. When I put the server name in the qualifier field in "attach to process" and click refresh, I can see the log on the remote machine saying that the host is connected but that is followed immediately by the above error. Lastly, and this may be the most important piece of information, when the authentication fails, I get an entry in the even log that states that a user account was locked out:
A user account was locked out.
Subject:
Security ID: SYSTEM
Account Name: MyHostComputerName$
Account Domain:
DomainWhichBothMachinesAreOn
Logon ID: 0x3e7
Account that was locked out:
Security ID:
MyHostComputerName \ MyUsername
*(which is identical on both machines)* Account Name:
MyUserName
Additional Information:
Caller
Computer Name: MyVirtualMachineName
I have read seemingly every tutorial, help ticket and random bit of information regarding this problem and remote debugging in general and tried just about every "quick fix". I would be very appreciative of any ideas. I can provide any additional information if needed. Thanks in advance.
"MyHostComputerName \ MyUsername" seems to indicate the VM service is trying to authenticate with a local user, not the domain user
have you created the same user & password as local accounts on both systems?
http://msdn.microsoft.com/en-us/library/ms164725.aspx
I had this same problem running VS 2010 Pro on Windows 7 Pro accessing Remote Debugger 2010 on Windows 2008 R2. I had created identical accounts on the server running the debugger and on my domain. I was running under my identical accounts both visual studio and remote debugger with administrator rights and with the firewall turned off. on both systems.
the error I got was "... the visual studio remote debugger on the target computer cannot connect back to this computer ..." I found this issue with both VS 2010 and VS 2005 so I knew it was an issue with my system
SOLUTION - add a local user account to your system running visual studio as a domain account won't work (you can run visual studio under the domain account, you just need the local account to be present with admin rights assigned).
I know this answer is for an old thread but there are a number of threads out there on this issue with no solution.
Go to target computer (that you want to debug remotely), open windows explorer and visit computer from which you are debugging. It will prompt for username password. Enter credentials for account that exist on both computers and has relevant permission. After it authenticates you will be able to use remote debugger.
My config was BOTH COMPUTERS IN WORKGROUP.
In my case when adding mu local computers credentials to remote host problem solved.
The credential is the workaround for the case when you have a "domain admin computer with vs studio" machine trying to remote debug a "non domain admin computer" machine from different domains.
Related
I am trying to debug an app, using Visual Studio 2017, that I will run on a virtual machine I've set up on my development system. The virtual machine runs Windows 10 (as does my development system).
I've installed the latest VS 2017 Remote Tools package on the virtual machine, and configured it. It is happily running on the virtual machine...but I can't connect to it from the desktop system.
When I do an attach to process, and a Find to find the system, the virtual machine is found.
However, after selecting the virtual machine, I am prompted for credentials. I've tried using the same login credentials I use to log onto the virtual machine, but that doesn't work. And there's no information shown as to what might be the problem.
The virtual machine is running under Hyper-V.
How do I go about setting up a remote debugging connection to virtual machine running on the same system where I am running VS 2017?
I ran into the same issue and managed to get it working, after much effort.
First, try switching the debugger authentication mode to "No Authentication" (Tools -> Options) and setting your project in Visual Studio to match (see the language-specific links in the MS docs link below). That will help you determine if it is a credential issue or something else.
The microsoft docs say, "You can run the remote debugger under a user account that differs from the user account you are using on the Visual Studio computer, but you must add the different user account to the remote debugger's permissions."
In my case, I ran the same account on both machines AND added my account to the debugger's permissions, and it still didn't work. We use Azure AD, and I was using a domain account. My VS computer was on the domain, and the VM was not (even though I could sign in with a domain account). After adding the VM to the domain, I could connect with "Windows Authentication" enabled in the debugger settings.
I'm trying to set up remote debugging across domains. My Windows 7 workstation running Visual Studio 2010 is on one domain and I'm trying to debug an ASP.NET app running in IIS 7 on a Widows 2003 server box in another domain. I have found many instructions on how to set this up, this being the best, most clearly written one: http://blogs.interknowlogy.com/2011/11/16/remote-debugging-from-visual-studio-2010/
However, I can only seem to connect to the remote debugging monitor on the server if Visual Studio is being run as the local user on my workstation, not as the domain user. This creates a number of challenges, such as loss of source control connectivity. When I try to connect using the domain user I get the following error: "Unable to connect to the Microsoft Visaul Studio Remote Debugging Monitor named 'username#servername'. The specified account does not exist." (I have substituted a generic username#servername for the actual values)
I have found a number of sources suggesting this will work with the domain user running VS2010 but have had no luck. Any idea what I might be missing?
Solved
First, i've read #KyleMit's answer on the same question and done all steps.
But, for across domain debugging also need to edit C:\Windows\System32\drivers\etc\hosts file on local computer.
Just add remote computer's ip address like this:
172.172.172.172 SRV-TEST-ADRESS
Where:
172.172.172.172 - ip address of your remote server
SRV-TEST-ADRESS - Server's name from Visual Studio Remote Debugger
Monitor on remote computer
You can know your server's ip address by ipconfig in cmd
After that, i could attach to proccess on remote computer across domain.
I have VS2010 on my dev machine (Win7) and I run a virtual machine under XP SP3 (name PC), on which I installed the VS2010 remote debugger, as well as .Net Framework 4.
On both OS I have the same user name (User), with the same password, with admin privilege, who is allowed to debug programs (Local Policy/User Rights Assignment/Debug programs). The firewall is deactivated on both.
When I debug my program through VS2010 (specifying "Start external program" and "Use remote machine"), I get
Error while trying to run project: Unable to start debugging.
Access is denied. Can not connect to Microsoft Visual Studio Remote
Debugging Monitor on the remote computer.
On the VM the Visual Studio Remote Debugging Monitor displays a line saying "PC\User connected".
If I try to attach a process using "Default" as transport and "User#PC" as qualifier, I get a similar error
Unable to connect to the Microsoft Visual Studio Remote Debugging
Monitor named 'User#PC'. Access is denied. Can not connect to
Microsoft Visual Studio Remote Debugging Monitor on the remote
computer.
Again on the VM the Visual Studio Remote Debugging Monitor displays a line saying "PC\User connected".
If I try to attach a process using "Remote (Native only with no authentication)" as transport and "PC:4015" as qualifier (changing the "Authentication mode" to "No Authentication (native only)", then it works and I see all the available processes on the VM.
Any idea on why the access is denied even if the Visual Studio Remote Debugging Monitor seems to accept the connection? Also if I 1st use "Windows Authentication" and try to start the debugger, and then I try to change the "Authentication mode" to "No Authentication", I get
Your new options can not be applied. Cannot stop server because one or
more users are currently connected.
View Msvsmon's help for more information.
I was eventually able to make it work by doing "Run as administrator" on VS.Net 2010 (I forgot that Windows 2008 and 7 are quite different when it comes to right management).
I'm trying to set up a remote debugger connection from my dev box on a domain to a web server (SERVER) in a workgroup with no success and I'm hoping for the some insight.
---------------------------
Microsoft Visual Studio
---------------------------
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor
named 'SERVER'. The Microsoft Visual Studio Remote Debugging Monitor
(MSVSMON.EXE) does not appear to be running on the remote computer. Please see
Help for assistance.
At this point, I have done the following:
I've installed the x64 debugging components, but not as a service. The monitor is up and running.
I've created an account on the workgroup machine to match my domain account in name and password.
I've granted this account the "Debug programs" right in Local Security Policy.
I've added this account the "Administrators" group.
Still I get the same error message.
Any suggestions?
You also need to create a local account on your dev box with the same name and password as your domain account.
This account just needs to exist - you don't need to run VS with it.
I need to do remote debugging of managed code (.NET) on a server hosted on a different network. Neither the client or server is on a domain so i have to use the public ip of the server.
I'm trying to use Visual Studio -> Attach to process -> default transport with the qualifier john#xx.xx.xx.xx but it's not working.
I get the error message : "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'john#xx.xx.xx.xx'. There is no server by the specified name running on the remote computer"
This error message tells me i can connect just fine but it can't find the msvsmon instance (which is 'john#WEB-001'). So i tried to use the combination of qualifiers such as WEB-001\john#xx.xx.xx.xx and xx.xx.xx.xx\john#WEB-001 but neither are working.
If I choose the transport "Remote (Native only with no authentication)" it connects just fine and I can see the process list on the server but it is pretty much useless because I can't debug managed code.
The administrator 'john' exists on both computer with the same password
Windows 2008 R2 X64 (Server)
Remote debugging component (VS2010) X64 installed
Firewall off
Msvsmon new server named 'john#WEB-001' running as john
Windows 7 X64 (Client)
Visual studio 2010 running as john
Firewall off
Any idea how to fix this, or is this scenario not supported? Thanks
having you tried putting web-001 in your hosts file, and connecting as john#web-001?
Try adding the server name to your hosts file:
192.168.1.100 WEB-001
Replace the IP with your own. Native code debugging is done over plain TCP/IP with no security but native code requires DCOM to enforce security, I don't understand the reason but ....
I know this is an old thread now but.
When the remote debugger is first installed you can set a firewall setting that allows all web traffic or only subnet connections. Run the configuration again to allow all web traffic.
Also, as the Administrator account, not a user in the Administrator group, Shift+r-click on the debugger shortcut to execute as a different user. Enter in the other user account that has the same username and password as the machine you are debugging with, in this case john.
This is the process I have to use.