Error: Remote machine does not appear in a Remote Connections dialog
If the remote machine does not appear in the Remote Connections dialog, check the following common causes.
If you are 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 is not 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.
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.
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for