Windows Server 2012 IIS 8.5网站远程无法访问求助（已开80端口防火墙规则）

Hey there, let's dig into why your IIS 8.5 site on Windows Server 2012 isn't accessible remotely—even after opening port 80 in the firewall. I’ve troubleshooted this exact scenario dozens of times, so here are the step-by-step checks to run through:

First, make sure your site is actually set up to accept external traffic:

• Open IIS Manager, right-click your site > Edit Bindings
• Confirm the binding is set to All Unassigned or your server’s public/remote-accessible IP address (not just 127.0.0.1 or localhost). Binding only to localhost means remote requests will never reach the site.
• Double-check the port is definitely set to 80—no typos here!

Sometimes the firewall rule is correct, but IIS isn’t even listening on port 80 for outside requests:

• Open Command Prompt as Administrator and run:

  netstat -ano | findstr ":80"
  

• Look for entries where the local address is 0.0.0.0:80 (listening on all network interfaces) or your server’s public IP followed by :80. If you only see 127.0.0.1:80, that’s the problem—your site isn’t configured to accept external traffic.
• If no port 80 entries show up, restart IIS with the command iisreset and check again.

Your server’s firewall might allow port 80, but other layers could be blocking traffic:

• Router Port Forwarding: If your server is behind a router, ensure port 80 is forwarded from the router’s public IP to your server’s private IP. Without this, remote requests hit the router and never reach your server.
• ISP Restrictions: Some ISPs block port 80 by default (to prevent unsanctioned public servers). Test this by temporarily switching to a different port (like 8080)—update the IIS binding and firewall rule, then try remote access. If it works, you’ll need to use an alternative port or contact your ISP to unblock 80.
• Antivirus/Firewall Overrides: Enterprise antivirus tools often have their own firewall features that can override Windows Firewall. Check your AV settings to confirm it’s not blocking incoming port 80 traffic.

Let’s diagnose the connection directly from the device trying to access the site:

• On the remote machine, open PowerShell and run:

  Test-NetConnection -ComputerName [your-server-ip] -Port 80
  

  Look for the TcpTestSucceeded value:
  • If False: Focus on network blockages (router, ISP, firewall).
  • If True: The issue is likely with IIS configuration or site content.
• Alternatively, use telnet [your-server-ip] 80 (enable Telnet via Windows Features if needed). A successful connection means the port is open; a timeout means it’s blocked.

If connections are reaching IIS but failing, the logs will tell you why:

• In IIS Manager, go to your site > Logging > note the log file path.
• Open the latest log file and look for entries from your remote IP address. The sc-status column will show error codes:
  • 403: Forbidden—check site folder permissions (ensure remote users have read access).
  • 404: Not Found—confirm your default document (like index.html or default.aspx) exists and is set correctly in IIS.
  • 500: Server Error—look for details in the log or enable detailed error messages in IIS to debug.

Sometimes the firewall rule looks correct but has hidden issues:

• Open Windows Firewall with Advanced Security > Inbound Rules
• Find your port 80 rule, right-click > Properties:
  • Ensure the rule is Enabled
  • Confirm Action is set to "Allow the connection"
  • Check the Profile includes the network your server uses (e.g., "Public" if accessing over the internet)
  • Make sure there’s no conflicting Deny rule for port 80—deny rules take precedence over allow rules.

If you run through all these steps and still hit a wall, share the output of the netstat command, relevant IIS log entries, or Test-NetConnection results, and we can narrow it down further.

内容的提问来源于stack exchange，提问作者SirG