使用1433端口Azure的输入端点被阻止？

问题描述

我运行它公开端口1433 WCF服务，这也被定义为输入TCP端点的Windows Azure工作者角色：

 ＆LT; InputEndpoint NAME =WcfServiceEndpoint协议=TCP端口=1433/＆GT;
 

同样的辅助角色也暴露TCP端口443上的其他服务，定义类似：

 ＆LT; InputEndpoint NAME =TcpInterfaceEndpoint协议=TCP端口=443/＆GT;
 

我看到在管理门户两个端点，我能够连接到TcpInterfaceEndpoint在端口443正确的，但我不能在所有连接至其他端口（从两个不同的计算机上这两者都是能够访问的尝试外SQL服务器，即没有被阻塞端口的传出连接）。当我试图在Azure实例（通过远程桌面连接）连接本地，远程登录连接确定。试图从其他地方连接与连接超时结束。一切似乎表明1433端口的处理方式不同端口443，并通过防火墙阻止的某个地方。我甚至试图完全禁用Windows防火墙在Azure实例，但什么都没有改变。

这似乎Azure是不会允许在端口1433的端点（这通常是MS SQL Server中，我们用它目前，由于在测试环境中防火墙限制），但我没能在任何地方找到此类限制的任何信息。所以 - ？是的话，还是我的地方做一些琐碎的误差

补充：我尝试另外一个测试：我换两个端口在配置文件中，这样WCF现在443和TCP运行在1433和，如我所料 - WCF服务是可用的，而TCP接口停止工作。我现在很相信1433，着实挡在某种方式。这纯粹是蛮好看的地方记载这些信息。

解决方案

下面是一些的我跑过有关港口被关闭（1433，1434，179）。

原因：端口179，1433和1434被阻挡在Windows Azure的公共使用，因此在这些端口的角色之间的任何连接将被阻塞，导致超时错误

解决方法：您必须连接到使用一组端口不包括端口179，1433，1434或端点的

I am running a Windows Azure worker role which exposes a WCF service on port 1433, which is also defined to be an input TCP endpoint:

<InputEndpoint name="WcfServiceEndpoint" protocol="tcp" port="1433" />

The same worker role also exposes another service on TCP port 443, defined similarly:

<InputEndpoint name="TcpInterfaceEndpoint" protocol="tcp" port="443" />

I see both endpoints in the Management Portal, I am able to connect to the TcpInterfaceEndpoint at port 443 correctly, but I am not able to connect to the other port at all (tried from two different computers which are both able to access SQL servers outside, i.e. the port is not blocked for outgoing connections). When I tried to connect locally on the Azure instance (via Remote Desktop connection), telnet connected OK. Attempt to connect from elsewhere ends with "Connection timed out". Everything seems to suggest port 1433 is handled differently to port 443, and is blocked by a firewall somewhere. I have even tried to completely disable Windows Firewall on the Azure instance, but nothing changed.

It would seem Azure is not allowing endpoints on port 1433 (which is normally MS SQL Server, we use it currently because of firewall restrictions in the testing environment), but I was not able to find any information on such limits anywhere. So – is it the case, or am I doing some trivial error somewhere?

Added: I tried another test: I switched both ports in the config file, so that WCF now runs at 443 and TCP at 1433. And, as I expected – the WCF service is available, while the TCP interface stops working. I am now quite convinced 1433 is, indeed, blocked in some way. It would just be fine to see this information documented somewhere.

解决方案

Here's some documentation I ran across about the ports being closed (1433, 1434, 179).

Cause: Ports 179, 1433, and 1434 are blocked for public use in Windows Azure, so any connection between roles on these ports will be blocked and result in a time-out error.

Resolution: You must connect to endpoints using a set of ports that does not include ports 179, 1433, or 1434.

这篇关于使用1433端口Azure的输入端点被阻止？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！