| description | title | ms.date | ms.topic | dev_langs | author | ms.author | manager | ms.subservice | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
If the remote machine does not appear in the Remote Connections dialog, check the following common causes. |
Remote machine does not appear in a Remote Connections dialog |
11/04/2016 |
error-reference |
|
mikejo5000 |
mikejo |
mijacobs |
debug-diagnostics |
If the remote machine does not appear in the Remote Connections dialog, check the following common causes.
::: moniker range="vs-2019" If you are using managed compatibility mode, please check the Visual Studio 2010 documentation: Troubleshooting Remote Debugging - Visual Studio 2010. ::: moniker-end
-
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.