Link to home
Start Free TrialLog in
Avatar of phirenetworks
phirenetworksFlag for United States of America

asked on

Cant access my default site in IIS 7 on 2008 SBS

Sooo, here we go...
Single server, win 2008 sbs.  Can't browse to default site, cant hit OWA on 80 or 443.  Default site has a ? on the icon next to it....  If I browse down to the OWA site in IIS, the choose browse on 443, it give me the SSC error; I click continue and it sends me to the evil "Cant display this page".

When we were first setting it up, it configured itself an IP of .3 and it got changed to .5 after the setup was complete.  Could this affect it?  

I realize that this is not much info - so feel free to fire questions this way.
Avatar of kagenokaze
kagenokaze

Only thing I can think of at this moment is to check your bindings by right clicking on your default site and going to edit bindings.  I am on server 2008 r2 so it may be a little different.
Avatar of phirenetworks

ASKER

I checked, and its has multiple - 443 isnt one of them, but 443 is bound to the web apps which has the OWA site in it....
ss.jpg
Avatar of Rob Williams
>>"it configured itself an IP of .3 and it got changed to .5 after the setup was complete."
You should run the "fix my network wizard" if the IP changed at some point, under SBS console | Network | connectivity
The IP is tied to the sites, DNS and much more.
Ran the wizard and still having the issue....
Just to verify; in IIS if you click on the "default web site", on the right under manage web site, it does show it has started?
Yes, all sites and started and I'm restarting it as I make changes just to make sure...
I have removed the extra bindings from he default site to simplify things - just 80 is bound now, and 443 is bound to the web apps site....still no go
Whats funny is that the browser is talking to the server bc it is presented with the certificate for a SSL site - but it will not access the directory...
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Nothing worked - and after letting 3 other people look at it I feel pretty confident its just jacked.  So I backed it up, and reformatted -- and poof, it works now!
While there was no returning from whatever had destroyed IIS - those solutions do fix a lot of problems like this....