Hello all,

I have a new DAG we setup with 4 server 2 in each site. Exchange 2013 on Serve 2008 R2.  When the database is activated on any server in site A, everything works perfect.  When the database is moved to site b, users sometimes have issues logging in to OWA and Outlook.  Both site have DC's in them.

Any ideas what could be wrong or where to start looking?

Thanks in advance for any help.

• Edited by CC_CalCon Sunday, May 17, 2015 1:31 AM

Hi,

I'm not sure, how you setup the servers. The following config should work and advise you to do a test with:

On SiteA CAS:
- set internal and external URLs
- set OWA authentication to forms-based (this bit probably doesn't matter)

On SiteB CAS:
- set internal URL *only*
- set OWA authentication to Integrated Windows

In general, it uses the proxying

Which CAS do you use for testing? Always the same? The CAS does the authentication not the mailbox role.

Hi CalCon,

Thank you for your question.

Did you means user cannot login OWA and outlook sometimes instead of all the times?

Did other users work fine if there is a user who didnt login OWA and outlook?

What is mean that you said When the database is moved to site B?

By my understand, database will failover when the member of DAG down and didnt move databases. We could make sure FSW is working without any problems. Then run the following command to  check mailbox database copy is working:

Get-MailboxDatabaseCopyStatus *

If we could not logon on OWA and outlook all the times, we could check if CAS 2013 could connect to Mailbox database server which is site B.

If we could not logon on OWA and outlook sometimes, we could check network problems between client and Exchange 2013 CAS. Of course it included between Exchange 2013 CAS and Mailbox server in site B.

We could check if there are any errors in application log and post them to ibsexc@microsoft.com for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim