Windows Server 2008 R2/IIS 7 拒绝所有外部 tcp 连接
例如，我无法通过 http 连接到全新安装的 64 位 Windows Server 2008。服务器位于域中，但不是 DC（这完全是另一个问题）。
IIS7正在服务器上运行，并且可以通过 http://localhost 在本地访问该网站，但是当我尝试从另一台计算机连接时在同一网络上，即使禁用 Windows 防火墙，连接也会被拒绝。
我可以使用 Windows 资源管理器连接并浏览服务器上的共享文件夹，因此这不是物理连接问题。我可以从服务器 ping 网络上的其他计算机，但尝试从另一台计算机 ping 服务器会导致“目标主机无法访问”。
据我所知，服务器拒绝来自任何机器的任何 TCP 连接。我在想，一定是我缺少了一些其他配置设置......请帮忙。
NS
I am unable to connect, for example, via http to a brand new installation of 64-bit Windows Server 2008. The server is on a domain, but is not DC (that's another problem altogether).
The IIS7 is running on the server and the website is accessible locally via http://localhost, but when I try to connect from another machine on the same network, the connections is refused, even though Windows Firewall is disabled.
I am able to connect to and browse the shared folders on the server using Windows Explorer, so it is not a physical connection issue. I can ping other machines on the network from the server, but trying to ping the server from another machine results in "Destination host unreachable".
As far as I can tell, the server refuses any TCP connections from any machine. I am thinking, there must be some other configuration setting that I am missing... Please, help.
NS
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
就像在 Windows 7 中一样，行为由操作系统认为它连接到的网络类型（家庭、工作、互联网）决定...即使禁用了防火墙，它也会尊重这些设置并相应地拒绝/允许连接...
Like in Windows 7 the behaviour is determined by the network type (home, work, internet) the OS thinks it is connected to... even with a disabled firewall it respects these settings and accordingly refuses/allows connections...
解决方案非常简单，这要归功于 ServerFault.com 上的 Ashley Steel 提出了正确的问题。事实证明，DNS 错误地解析了服务器的名称，因为该计算机的名称与曾经位于同一子网上的已退役的旧工作站的名称相同。
解决方案：重命名服务器。
NS[现在躲在岩石下]
The solution is embarrassignly simple, and the credit goes to Ashley Steel, on ServerFault.com for asking just the right questions. It turns out that the DNS was resolving the name of the server incorrectly, because the machine was named the same as an old, since decommissioned workstation that used to live on the same subnet.
The solution: rename the server.
NS[Now hiding under a rock]