I have 2 AD sites - one internet facing and the other not. I am also using and Edge server. OWA for a user account at each site works if I use the URL for that server. I have a published URL that is accessible form the internet and I need to be able to use that same URL internally. The external URL works for the internet facing site, but not for the other site. I have changed the OWA virtual directory on the non-internet facing site to use integrated windows auth but now I get an error for users on that site that says "Outlook Web App isn't available". For OWA, both servers have the internet URL configured for the internal name and only the internet facing server has the external URL configured. This is Exchange 2010 SP1 with all latest rollups. Please help!!!

Hi Eric, Can you push a AD replication from internet facing site to non facing site and check after some time.Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

Hi Eric, Some information for you: http://technet.microsoft.com/en-us/library/bb310763.aspx http://social.technet.microsoft.com/Forums/en/exchangesvrdeploy/thread/894c1894-8f8b-47ca-a56f-5fc5e0b8057d Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I have read both those threads and that is where I got the ideas for what I have tried. When I try to access an account via OWA that resides on the server at site B I get an error page that states "Outlook Web App isn't available. If the problem continues, please contact your helpdesk."

Exchange on the Internet facing site, configure Exernal URL On Exchange in the non internet facing site, dont configure any external URL's and configure Windows Integrated authentication for OWA and other services running in IIS. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

That is exactly the configuration that I have... If I use the public URL and log in to an account on the internet facing CAS it works perfectly. If I use the same public URL and log in to an account on the CAS server at the non-internet facing site I get "Outlook Web App isn't available. If the problem continues, please contact your helpdesk.". If I use the internal URL to the non-internet facing site, I do not get a forms based login but after providing login credentials OWA loads properly. When configuring Windows Integrated Authentication, I am assuming that the only place I need to do that is in the ECM? That is where I made the change. What could be causing this?

OK...it is working now. I think what happed is that some Exchange services were not starting up properly on the site B server. I restarted the Exchange Active Directory Topology services and almost every Exchange service was also restarted. After that, OWA was working as desired. Thanks!