Can't start default site - port 80 in use.

[MasterRacker]

Windows server 2012 R2 with IIS 8.5

I have a purpose built server for running a single web base application that uses IIS and SQL server. It has been running fine until today after a reboot. The application runs out of the default site on port 80 and used to come up automatically after a restart. Today I am trying to start is manually via IIS Mgr and getting a message saying it can't start because something else is using port 80. Running "netstat -aon" shows only the system task under PID 4 listening on port 80. From what I can find on the web, that is normal behavior. If I bind the default site to port 81 it will start but that is not an acceptable solution and when I revert to port 80 it fails again. Using Sysinternals Process Explorer I have been unable to find anything rogue running on the server. I've seen references to the registry key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\ListenOnlyList" however that appears to be default and means the system is listening on 0.0.0.0.

I've found a number of online solutions involving identifiable applications taking over port 80, bt this server is running nothing but IIS.

Anyone have any ideas?

Jeff
[small]"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me

http://RusticPhoto.org

[/small]

 

[MasterRacker]

Update: I've backed out the 2 windows updates that installed this morning, rebooted and continue to have the same problem.

Jeff
[small]"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me

http://RusticPhoto.org

[/small]

 

[SamBones]

Have you pointed a browser at it to see if anything comes up?

 

[MasterRacker]

Browsing to the server from the outside and to

http://localhost

from the server itself give http 404 page not found errors, so nothing else appears to be running that way either.


Jeff
[small]"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me

http://RusticPhoto.org

[/small]

 

[gbaughma]

Does a
netstat -a | Find ":80"

... give you any help?


Just my $.02

"What the captain doesn't realize is that we've secretly replaced his Dilithium Crystals with new Folger's Crystals."

--Greg

 

[MasterRacker]

The only instance is the System task using PID 4. From what I've read, this is normal. I've send references to telling http.sys not listen on port 80, however that's usually for things like trying to get Apache and IIS to coexist. In any case, the method to disable that is through hidden devices in device manager, and in my case the HTTP driver does not show up when I show hidden devices.

I've also done "net stop http" to see which services are dependent on http besides web publishing. In this case I disabled Print Spooler and Windows Remote Management with no luck.

Jeff
[small]"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me

http://RusticPhoto.org

[/small]

 

[MasterRacker]

Update:
I've given up on his problem and have been able to move the site to port 81. Long term this might be more stable since that's non-standard. I've seen a number of references to these exact circumstances around the web and none of them show a solution so I'm not alone.

Thanks for the suggestions.

Jeff
[small]"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me

http://RusticPhoto.org

[/small]