Windows 2008 r2 server - cannot start apache on port 80

Question

I have a rackspace cloud server with a Windows 2008 r2 server. I uninstalled IIS because I want to install Apache.

I installed Apache, but it fails every time I try to start it when I listen to port 80.

I ran the netstat -aon command | finderstr is "80" and I see the following:

C: \ Users \ Administrator> netstat -aon | findstr "80" TCP 0.0.0.0:80 0.0.0.0:07 LISTEN 4 TCP 10.180.15.249:139 0.0.0.0:08 LISTEN 4 TCP [::]: 80 [::]: 0 LISTENING 4 UDP 10.180.15.249: 137: 4 UDP 10.180.15.249:138: 4

So what are those running on port 80 and why can't I start apache? Is there an alternative port to run apache that will work the same as 80?

Answer 1

To enable port 80 on Windows Server 2008 R2 :

NOTE. IIS is not installed . I added this firewall rule to enable Apache to connect to a port on port 80.

• Click Start-> Control Panel-> Windows Firewall
• Click Advanced Settings in the left pane of the Windows Firewall.
• Click Inbound Rules in the left panel Advanced Options
• Click New Rule ... in the right pane of the Actions.
• Select "Port" and click "Next>"
• Select "TCP", then "Specific Local Ports:" (should already be selected)
• Enter 80 in the field (number only) and click "Next>"
• Select "Allow Connection" and click "Next>"
• Leave all profiles verified and click "Next>"
• Enter a name and click Finish.

Your server should now be able to accept connections on port 80.

Answer 2

On a Windows server running MSSQL, disabling the MSSQL ReportServer services (display name: SQL Server Reporting Services (MSSQLSERVER)) and World Wide Web Publishing services resolved the issue for me. No need to bother with the firewall settings or change the default port configurations.

Answer 3

I am running Windows 2008 r2 with IIS and sql server. I added an additional IP address to run apache and configured IIS to bind to one of the IP addresses. I ran into the same problem and found suggestions about disabling SQL Reporting Services and WinRM. These solutions did not work for me.

There are many different services that can use the api HTTP server (http.sys) and then simply display as pid 4.

I found the answer from the link below. The essence of the link is to go to the command line.
Type netsh press enter.
Type http and press enter. Add iplisten ipaddress = xxxx

http://msdn.microsoft.com/en-us/library/cc307219(v=vs.85).aspx

There is also a method to disable http.sys in the registry, but I do not know what the consequences may be.

I hope this helps someone else so that they do not spend as much time as trying to find a solution.

Answer 4

I found that I can successfully add firewall rules so that my own server runs on port 80 in the vshost visual studio debugging environment, but when started as a service, it only works on the local host from the computer, and not from external hosts.

Very frustrating. It looks like there are possible conditions in the firewall that are not explicitly displayed in the Windows Firewall configuration interface.

Answer 5

When installing IIS, you need to change the bindings on websites in IIS so that no one uses "all available addresses": 80 bindings. Either change the ports or change the listening IPs.