Configure Firewall for Remote Debugging Dialog Box
Note
This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
This dialog box appears when the Windows Firewall blocks the debugger from receiving information over the network. To continue remote debugging, you must open a hole in the firewall so the debugger can receive information.
Caution
Opening a hole in the Firewall may expose your machine to security threats that the Firewall is designed to block. Opening a hole for remote debugging unblocks ports 4020 and 4021 in Visual Studio 2015. In other versions of Visual Studio, other port numbers are used. For more information, see Remote Debugger Port Assignments. In addition, it allows the debugger to open additional ports. For more information, see Configure the Windows Firewall for Remote Debugging.
UIElement List
Cancel remote debugging
Cancels the remote debugging attempt. The security settings of your machine remain intact.
Unblock remote debugging from computers on the local network (subnet)
Enables remote debugging of machines on your local subnet. This may open vulnerabilities to machines on your local subnet, but the firewall continues to block information coming from outside the subnet.
Unblock remote debugging from any computer
Enables remote debugging of machines anywhere on the network. This setting is the least secure.
See Also
Debugger Security
Set Up the Remote Tools on the Device
Debugging User Interface Reference