• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Great, OWA is borked now... help please? (Exchange 2003)

M

Mizugori

Senior member
Have Windows Small Business Server 2003, had to go through a whole nightmare of reinstalling Symantec Endpoint because the last r-tard here didn't do it properly and it was not working. I mention this because Endpoint creates an entry in IIS and I don't know if this is part of the problem. Also, I changed some settings in IIS a while ago to make a simple 'under construction' page appear instead of any random idiot who happened to type in our website being greeted by the 'windows server 2003 company internal site' web console thing, that I did not feel the outside public should have access to.

So, in brief, I know *jack shit* about IIS, and OWA, and etc. I just need to get OWA working again, because it used to be that you could just type mail.OURSITE.com from anywhere and get access to outlook. When I fixed Endpoint, and/or changed the website thing mentioned above, I apparently broke it. Now if you type mail.OURSITE.com you just get the same construction page thing.

Can anyone help?
 
What exactly were the steps you took between the last known functional access of OWA and now?
 
interesting! when i try that, it says:


Secure Connection Failed

mail.OURSITE.com uses an invalid security certificate.

The certificate is not trusted because it is self signed.

(Error code: sec_error_ca_cert_invalid)

* This could be a problem with the server's configuration, or it could be someone trying to impersonate the server.

* If you have connected to this server successfully in the past, the error may be temporary, and you can try again later.
 
Do you know how to access IIS to view the cert on Exchange? Without a valid Cert it should not naively attempt to show OWA as SSL is required by default for the logins.
 
Im betting the cert is fine but because the settings were changed on the default page the url no longer matches the cert hence the mismatch. I would change the settings back to the original method and instead put a redirect in to the owa login or something.
 
It's possible the external URL for OWA was reset, then? I'd check the OWA configuration and verify the external URL is accurate.

I use Exchange 2007 so my layout is quite a bit different or I'd give you more detailed steps.
 
I would revert what you did with the construction page view modification you mentioned.

IIS is the Microsoft Webserver that hosts OWA. Start screwing around with IIS settings and you definately will break OWA access.

Secondly, if you are using Internet Explorer, make sure you turn off "Friendly error messages" settings under Internet Options. That Secure connection failed error seems odd, but not unusual for self-signed SSL certificates to be used in environments like this. Can you continue on to login to OWA?
 
I don't administer our email system but I did recently have conversation with the person who does. We are using Exchange 2003 BTW. After the identical problem you describe, he told me that installing Symantec Endpoint protection has a known problem with OWA and basically hoses it. I don't know what he had to do to fix it, but since its a known issue, I suspect you can find it by searching the Symantec support site.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top