Configure Firewall for Remote Debugging Dialog Box
This dialog appears when the Windows XP SP2 Internet Connection 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 Internet Connection Firewall may expose your machine to security threats that the Internet Connection Firewall is designed to block. Opening a hole for remote debugging unblocks DCOM (TCP Port 135) and IPSEC (UDP 4500 / UDP 500). In addition, it allows the debugger to open additional ports. See How to: Set Up Remote Debugging for more information. |
- 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.
Caution