Volleynerd Knowledge Base

Sunday, August 14, 2011

Who's Hogging Port 80


Ready to re-install WIRNS after a machine rebuild, and it has to be on port 80 (Replays only talk on that port). Fine - I move IIS to another port. But, WIRNS installer says it's still in use.

Long story short, it's not IIS (it *was* on 80, but I moved it), lots of peeps on the tubes saying various other processes: SQL Reporting Services was the most popular.

For me, it was Web Deployment Agent Service. MS docs about it here.
Even with IIS running on 80, it's somehow *sharing* that port, and sticks around after IIS has been moved. Telnet localhost 80
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Sun, 14 Aug 2011 21:11:43 GMT
Connection: close
Content-Length: 326


Anyway - I'm not remote deploying anything to this box, so this service is now disabled. Port 80 - free again!




Comments: Post a Comment

Home