Visual Studio 2013远程调试所需的防火墙端口 [英] Firewall ports needed for Visual Studio 2013 Remote Debugging

问题描述

我有一个第三方防火墙阻止VS 2013 Update 2远程调试.我希望我们的域管理员打开必要的端口，但文档中似乎存在差异.

I have a 3rd party firewall blocking VS 2013 Update 2 Remote Debugging. I want our domain admin to open the necessary ports, but there seems to be a discrepancy in the documentation.

在线版本提到:

DCOM(TCP端口135)和IPSEC(UDP 4500/UDP 500)

DCOM (TCP Port 135) and IPSEC (UDP 4500 / UDP 500)

已安装的文档中提到:

...为此，请允许msvsmon.exe正在侦听的TCP/IP端口上的通信.默认情况下，它们是端口4018和4019，其中4018用于所有操作系统，而4019仅用于Windows x64以允许调试x86进程.

...To do so, allow traffic on TCP/IP ports that msvsmon.exe is listening on. By default, these are port 4018 and 4019, where 4018 is used on all operating systems, and 4019 is used only on Windows x64 to allow debugging x86 processes.

没有提及DCOM/IPSec.我知道从Remote Tools 2012开始有架构上的变化，但是我不知道这是否意味着DCOM和IPSec从那以后就被丢弃了.我在安装的文档中看到Windows 7和Windows Server 2008 R2附带的Windows Web Services API(它们恰好是我的本地/远程版本).这是否可以取代DCOM和IPSec体系结构?

No mention of DCOM / IPSec. I know there was an architectural change starting Remote Tools 2012, but I don't know if it means that DCOM and IPSec were dropped since then. I've seen in the installed documentation mention of the Windows Web Services API, shipping with Windows 7 and Windows Server 2008 R2 (which happen to be my local/remote versions). Does this perhaps replace the DCOM and IPSec architecture?

底线-对于该特定版本，我需要打开哪些端口?

Bottom line - which ports do I need to open for this particular version?

注释:编辑人员请勿删除"Update 2"一词，远程工具具有与不同Visual Studio 2013版本相对应的不同版本.

推荐答案

我最近使用Visual Studio 2013 Update 3对AWS EC2实例进行了远程调试.

I recently tested remote debugging with Visual Studio 2013 Update 3 to an AWS EC2 instance.

我只需要TCP 4018-4019的入站安全组规则.

I only needed inbound security group rules for TCP 4018-4019.

(以前在Visual Studio 2012中，我只需要TCP 4016-4017的入站安全组规则.)

(Previously with Visual Studio 2012 I only needed inbound security group rules for TCP 4016-4017.)

这篇关于Visual Studio 2013远程调试所需的防火墙端口的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！