Exchange 2010 OWA not working

exchange-2010outlook-web-appwindows-server-2008-r2

So here's an interesting problem that just started happening today. OWA is no longer working on the internal network or Externally. I now get an error in IE saying:

"Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://server again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator. "

Yet in IE, TLS is enabled and SSL 2 & 3 have been disabled. I used IISCrypto on my Exchange 2010 server and it shows I am running with best practices.

I've also tried rebuilding my OWA Virtual Directory with no success.

I don't see any obvious errors in Event Viewer.

What could I be missing?

Another note, email is being forwarded to my exchange box from my mailmarshall server but external email is not showing in mailboxes. Only internal emails are.

Best Answer

Exchange rarely does anything on its own - so if it has only happened today - what has changed? Something will be logged.

Is this a single server of multiple? How did you rebuild the virtual directory? Can you browse to the root of the site? If not, then the issue is probably with IIS rather than Exchange. Check the correct bindings are in place on the default web site.

Related Solutions

Exchange 2010 Hub cannot deliver to Exchange 2007 Hub – “451 5.7.3 Cannot achieve Exchange Server authentication”

Finally tracked down the cause. Our Cisco ASA firewall was to blame.

From http://jamesosw.wordpress.com/2009/12/30/exchange-hub-transport-unable-to-communicate-at-different-active-directory-sites/:

If you happen to be deploying Exchange 2007/Exchange 2010 Server in a multiple sites environment and using a Cisco ASA Firewall as your VPN tunnel, you’ll likely encounter issues below:

Users are only able to send emails within the same Active Directory site

When users attempt to send an email over to the next hop/Active Directory Site, under the Exchange Queue, you’ll see a Retry status: 451 4.4.0 Primary target IP address responded with “451 5.7.3 Cannot achieve Exchange Server authentication” SMTPRelay to remote AD Site

When you attempt to telnet from the Exchange Servers from both site, you’ll get such response from the telnet command: 220*************

The only way to fix this is to use the Commandline Interface (CLI) and type in this command:
telnet YourCiscoManagementIP

device password (default is usually cisco)

en

password (Management password)

no fixup protocol smtp 25

write mem
Remember to run these command all firewalls at each site. Once is done, telnet to the Exchange server with port 25 and you should get a normal response:
 220 ExchangeServerHostName.Domain.com Microsoft ESMTP MAIL Service ready at Day, Date Month Year, Hour:Minute:Seconds +TimeZone

As soon as we did this on the ASA, mail started flowing without hassles.

Exchange 2010 OWA send connector issue

You likely only need one send connecter, and since your primary mail server is remote, I assume you want to send email through it (aka smarthost). That way you don't need to worry about DNS A records, MX, PTR, SPF, and all the other mail configuration stuff. Just set your send connector smarthost to your mail provider's SMTP server and ensure you are authenticating so you'll be allowed to relay. If you don't authenticate, they'll almost surely deny your email (which is likely why it's sitting in queue) because that would be a "open relay", which is a bad thing.

Best Answer

Related Solutions

Exchange 2010 Hub cannot deliver to Exchange 2007 Hub – “451 5.7.3 Cannot achieve Exchange Server authentication”

Exchange 2010 OWA send connector issue

Related Topic