The remote debugger may be running under a different user account. This message may occur for several reasons:Ī DNS issue is preventing the connection. The remote computer exists, but Visual Studio could not connect to the remote debugger. The requested name was valid, but no data of the requested type was found To get the correct version of the remote debugger, see Remote Debugging. The remote debugger version does not match Visual Studio. Make sure the firewall is not blocking your request, especially if you are using a third-party firewall. This message may occur for several reasons: Visual Studio could not connect to the remote debugger. There is no server by the specified name running on the remote computer Otherwise, try restarting Visual Studio with Administrator privileges, and then try again.Īn internal error occurred. If you are trying to connect using a host name, try an IP address instead.Ĭheck the application log on the server (Event Viewer on Windows) for more detailed information to help resolve the issue. If you are using Attach to Process to debug: If you are debugging an Azure App Service app, try using the Attach Debugger command from Cloud Explorer or Server Explorer instead of Attach to Process. Connection with the remote endpoint was terminated
#Ms visual studio remote debugging monitor windows#
If these values are correct and the message mentions Windows Authentication mode, check that the remote debugger is in the correct authentication mode ( Tools > Options). In the Attach to Process dialog box or in the project properties, make sure that the remote computer name and the port number matches the name and port number shown in the remote debugger window. If these steps do not resolve this error, see The remote machine is not reachable.Ĭonnection request was rejected by the remote debugger This will show processes if you are connected under a different user account. If you are attaching to the process and you connect successfully but don't see the process you want, select the Show processes from all users check box. Make sure that the version of the remote debugger running on the target machine matches your version of Visual Studio. If the computer name does not work, try the IP address and port number instead. The port number must match the port number of the remote debugger, which must be running on the target machine. The computer name must be the following format: Make sure that you enter a valid computer name and port number in the Attach to Process dialog box or in the project properties (To set properties, see these steps). The debugger was unable to resolve the specified computer name The debugger cannot connect to the remote computer.
![ms visual studio remote debugging monitor ms visual studio remote debugging monitor](http://3.bp.blogspot.com/-l_yGvPgiHnc/T6KoyC_IR_I/AAAAAAAAAFE/z1kr89wgeqg/s1600/New+Picture+%281%29.png)
![ms visual studio remote debugging monitor ms visual studio remote debugging monitor](https://i.stack.imgur.com/oX4Pa.gif)
![ms visual studio remote debugging monitor ms visual studio remote debugging monitor](https://docs.nvidia.com/nsight-visual-studio-edition/install-setup/graphics/nsight_monitor_general_sync_dir.002.png)
This message may occur because the remote debugging monitor is not properly set up on the remote machine or the remote machine is inaccessible due to network problems or the presence of a firewall. Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor