Hi:
I looked at the prior thread which was marked as answered but seemed to stop without your agreement that the suggestions helped. So we are left in a quandary as to what to suggest next because we don't know if the events of March were resolved and this is a new development or a continuation of the same. Can you tell us if the bindings are set as Grey suggested? And answer the question about other web stuff?
"I suppose check the bindings on the default site in IIS Admin. It is normally set to all unassigned. Have you installed any other web stuff, media servers, etc?"
So only a new install of something causes the Web Page to not start after rebooting the server? A simple restart has no effect?
What are the bindings like when working and what are they like when not working? Can you put up a screen shot of both conditions? And if you change them to the "working" condition does that improve things without a subsequent restart? Or will it "usually" stay working until something further is installed such as an Windows update?
What other programs use IIS as their interface? We can compare that list to a known good Essentials server.
- Marked as answer by LJSEA Thursday, September 03, 2015 5:04 PM
You need to run Roberts tool. Not sure why you have that warning about no default ssl site
http://titlerequired.com/2014/02/14/windows-server-essentialsconfiguration-troubleshooter/
I got this:
Binding Missing : Default Web SiteWebsite Name : Default Web Site
Binding : http*:80:-------------.remotewebaccess.com0
I blanked out the first part of the web access but it was correct.
The *ONLY* reason this would not work is if you installed some web app on the server. Not that you can't install things, you just have to know how. It is very easy to Google what is using port 80, but you prob already know.
In any case your bindings are wrong. I would go to the dashboard, settings, Anywhere access and configure again to correct it