• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2258
  • Last Modified:

Restarted SBS 2008 and OWA stopped working!

Hello,
I just restarted my SBS 2008 box and now I have no access to OWA.  I have a feeling its an SSL issue.  Can anyone help?
0
SteveMat11
Asked:
SteveMat11
  • 24
  • 9
  • 4
  • +1
1 Solution
 
Dustin99352Commented:
What does it say when you attempt to access OWA?
0
 
AustinComputerLabsCommented:
Did you recieve any errors?
Try restarting IIS.
Can you access any portion of the default website?
0
 
SteveMat11Author Commented:
Cannot access any portion of the default website.  It gives me the usual IE cannot display the webpage.  I received no errors on startup.  Tried several times to iisreset.

Thanks for the help guys, im going nuts here.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
AustinComputerLabsCommented:
Are you connecting to an IP or a URL?
Try the https:// IP /OWA
If that works it is a DNS issue.
0
 
SteveMat11Author Commented:
Nope, tried them all.
0
 
Dustin99352Commented:
go to run and type services.msc

Scroll down to the Microsoft Exchange services and make sure they are running.
Make sure that IIS is started in the console as well.  It's quite possible it isn't, and that's why you're recieving the issue.

If you don't see anything on those two, then go to server manager, diagnostics, and look at the events under system, and under applications for Microsoft Exchange and see if anything is popping up in there.
0
 
SteveMat11Author Commented:
I have two sites running under iis.  The second site is non SSL and is running fine.  Its just my default which redirects to /owa that isnt running.  When i look at ssl settings they are all grayed out.  All services are running.  
0
 
AustinComputerLabsCommented:
Are you attempting to connect from whithin the LAN?
Can you ping the URL?
0
 
SteveMat11Author Commented:
im sorry the site is running according to iis however cant display a page.
0
 
SteveMat11Author Commented:
I am connecting from outside.  I cannot ping the URL however I can RDP the machine by using the URL.  Doesn't make any sense to me.
0
 
Dustin99352Commented:
Did you check the MS Exchange Services?  
0
 
AustinComputerLabsCommented:
If you have not tried to ping the URL in the past, the router may be set to ingore ping requests to protect from DOS attacks.
You are attempting to connect to OWA through the browser on the server in question?
0
 
WalkaboutTiggerCommented:
With the SSL-related settings grayed-out, it implies you have no SSL certificate associated with the website.  Regardless of this, let us start with the basics.
From the IIS console, when you select the Properties of the default website, what IP address is it assigned to?  Does it have any host headers associated with it?
On the Documents tab, what is the default document?
If you have a redirect in place from the root of the default site, are you being correctly redirected or are you being redirected to an HTTPS URL?
If you go to the Server Certificate dialog, does the server have a certificate in the Certificate Store?  If so, have you attempted to reassign it to the site?
For what reason was the server rebooted?  Had anything changed prior to that reboot?

0
 
SteveMat11Author Commented:
Its assignesd to 192.168.1.95:80 which is correct, default doc is index.htm on top.  Dont see anything about host headers.  It is correctly redirected.  Where do I find info on the cert?  Im in iis7.  Nothing has changed prior to reboot.  I had to reboot because mail was getting held up at my 3rd party spam company.  It was getting an "out of resources" error.  Mail has since been delivered after reboot however owa will not work.
0
 
SteveMat11Author Commented:
Ahhh.... when I click SSL settings under default site an alert pops up in the top right corner saying this site does not have ssl bindings and cannot accept ssl connections.  
0
 
SteveMat11Author Commented:
Were making progress... I added port 443 to bindings since it was missing and now i get redirected to an IIS error, "404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable."
0
 
WalkaboutTiggerCommented:
You'll actually need to assign an SSL certificate to the server and not just bind port 443.

If you open the Properties of the website and go to the Directory Security tab and select Server Certificate, do you have an option to assign a certificate?

If so, select that option and see what certificates it show you as eligible to be installed.
0
 
SteveMat11Author Commented:
There was a pull down of all of the certs and I attached one to it.  When I open the site in IE i see the lock and when I click it the correct godaddy cert appears.  Just getting a 403 error from iis.
0
 
SteveMat11Author Commented:
im sorry 404 not 403
0
 
WalkaboutTiggerCommented:
what is the URI that is giving a 403?

Https://host.domain.com/?????
0
 
SteveMat11Author Commented:
yes, 404 not 403
0
 
SteveMat11Author Commented:
I can access in on the server from https://localhost/owa
0
 
SteveMat11Author Commented:
Does anyone have ideas why I can see the OWA login page if im in the server and i point IE to https://localhost/owa however if I try that (replacing the localhost with the ip obviously) I get a 404 error??  Any help is greatly appreciated.
0
 
SteveMat11Author Commented:
Why is it that https://localhost/owa works however if I replace localhost with my external IP address I get a 404 error?
0
 
WalkaboutTiggerCommented:
What IP addresses is the default website bound to?
You said you have another website on the server - what IP addresses and ports are it bound to?
0
 
SteveMat11Author Commented:
The default website is bound to: http    mail.mydomain.org   80   192.168.1.95 (.95 is exchange)
                                                     https                                  443   192.168.1.95

443 has the mail.mydomain.org SSL cert selected.


The other site has 1 entry for http     80 192.168.1.99


The other site is non SSL and works fine.  I can access it externally.  The OWA however I can only access from the server itself by using "localhost" as opposed to the ip address.  I DONT GET IT!
0
 
WalkaboutTiggerCommented:
So going to http://192.168.1.95 performs the redirect to what URL?

Does it go to https://192.168.1.95/owa or is it something different?

I presume the 443 is listed under Secure Socket Layer and not at the top.
0
 
SteveMat11Author Commented:
http://192.168.1.95 returns an IE error HTTP 404 not found.
https://192.168.1.95/owa returns Server error 404, looks like a friendlier message, not the IE default.  by typing 192,168.1.95 it should redirect to the https version with /owa at the end.

What do you mean by 443 is listed under SSL and not at the top??  In the bindings?  Yes, it has an https next to it.
0
 
WalkaboutTiggerCommented:
So if you look at the virtual directory configuration for the OWA directory and select Properties, what is the default document?  If you look in the directory, does that document exist?
0
 
SteveMat11Author Commented:
All there.  I noticed that when I right click default website and choose browse, IE opens and it tries opening a page that is https://mail.mydomain.org/owa/owa.  Is there supossed to be two /owa's at the end?  I checked the redirect and its there only once, not sure of why its putting a second one in.  Can this be the issue?  I have a feeling something is wrong with either the bindings or the redirect for either the default website or the SBS web applications site.  Which one should I be working with?  Weird how all of these problems after a simple reboot with no application changes or updates installed.  Thanks for all your help by the way, im completely lost/frustrated!
0
 
WalkaboutTiggerCommented:
Do you have any  stopped websites on the server?
0
 
SteveMat11Author Commented:
nope
0
 
WalkaboutTiggerCommented:
In SBS2008, OWA is in the SBS Web Applications site by default.  This is the site that should have the SSL cert installed.

Verify the OWA virtual directory exists in the SBS Web Applications site.
0
 
SteveMat11Author Commented:
The OWA virtual directory is there.  How do I make sure the cert is installed there?  If I check the bindings of the SBS Web Applications I have two entries:

http   80    *(under IP address)
https 443  * (under IP address)  If I hit edit the correct SSL Cert is selected from the dropdown.
0
 
SteveMat11Author Commented:
Also if I look at the SSL settings under the SBS Web Applications the require SSL box isn't checked.  (However I tried checking it and it still doesn't work)
0
 
WalkaboutTiggerCommented:
So which IP is this site bound to?  If you go directly to https://ipaddressOfSBSWebApps/owa do you still get the 404 error?

If so, what service pack is installed?  You may need to reinstall the service pack.  404 errors for OWA in SBS can be caused by a corruption which can only be resolved by reinstalling the SP.
0
 
SteveMat11Author Commented:
I get the error however if I enter that URL it redirects to https://IPAddress/owa/owa.  Not sure why its throwing the extra owa in there.  If I use local host it works fine so not sure anything is corrupt.
0
 
SteveMat11Author Commented:
If I give you RDP access would you mind taking a look?
0
 
SteveMat11Author Commented:
What bindings should I have listed for the default site and what should be under SBS Web Apps?  I think there may be a conflict here somewhere.
0
 
SteveMat11Author Commented:
Fixed it, it was a binding issue.  I had two conflicing that cause the double /owa's.  Sorry for this mess!  Points will be awarded to you for all your help.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 24
  • 9
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now