Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
If the remote machine doesn't appear in the Remote Connections dialog, check the following common causes.
If you're using managed compatibility mode, please check the Visual Studio 2010 documentation: Troubleshooting Remote Debugging - Visual Studio 2010.
Common causes for this error
The remote machine is running on a machine that is in a different subnet. To fix this, manually type the machine name or IP address in the Qualifier dialog
The remote debugger isn't running on the remote machine. To fix this, start the remote debugger.
The firewall is blocking communication between Visual Studio and the remote machine. To fix this, configure your firewall to allow Visual Studio and the remote debugger (msvsmon) to communicate. For more information, see Configure Windows Firewall for remote debugging.
Antivirus software is blocking communication between Visual Studio and the remote machine. To fix this, configure antivirus software to allow Visual Studio and the remote debugger (msvsmon) to communicate.