This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Recently I was working on an issue, where customer was not able to browse the Default website hosted on IIS over port 80 and the error was:
Initial thought was, definitely the port is blocked...but who was blocking the port was the biggest question???
So, I started the investigation with basic isolation steps:
- Created a different test site with binding port 80 (by stopping the Default website as we cannot run two sites with the same port together). But the test site also failed with the same error.
- Created a different IP: Port 80 binding and it worked. Tested it on the default website and there also it worked.
- Checked on the customers machine if they had enabled any sort of proxy or firewall that might be blocking the port 80 particularly but that wasn't the case for the customer.
- I also ran the Port Query tool and there also I got the error that Port is being used: Port Query Tool
- Next, ran the below command to see what all services are listening on port 80 and nothing was useful:
netstat -ano |findstr 80
After doing some research, I found out that we have a service on the windows server called as "Sync Share service " that also by default uses the same port number 80 as IIS Default Web Site.
Now, what is a Sync Share service???
Work Folders is available in Windows Server 2012 R2 Essentials as part of the File and Storage Services role. Work Folders uses the IIS Hostable Web Core feature and all management is performed via the Work Folders canvas in Server Manager as well as via Windows PowerShell cmdlets. Windows Server Essentials is managed via its dashboard and the IIS Management UX. Both products assume exclusive access of the SSL port (443) and HTTP port (80). This is the default configuration for both products.
In my case, the customer had the service enabled but was not using it, so we stopped the service from the Services.msc window and continued using the Port 80 for the IIS hosted web applications.
Now, if you would like to keep using both the services on the server, then you would need to change the port number for one of the services.
We have a very good article written about the same in this article: Port Conflict Issue in 2012 R2
Hope this article helps everyone 