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

Exchange 2007 OWA over 2 Sites

Hi All,

Exchange is already up and running in one of AD Sites (US). Yesterday, I installed another instance of the exchange server in a different site (UK). All appears well so far, except:

When I launch OWA from the new UK box, and try to login to a mailbox hosted in the US site, I get the following error:

Outlook Web Access is not available for the user mailbox that you are trying to access. If the problem continues, contact technical support for your organization and tell them the following: A Microsoft Exchange Client Access server in the mailbox Active Directory site is incorrectly configured for service discovery. The host name entry should be in the format "http<s>://<host name>[:<port>]/owa", but is stored as "https://usowa.xxxdomainremovedxxx.com/".

Does anyone know what could be causing this? I assumed the browser would redirect to the US OWA URL and log me into the mailbox?

Mant thanks,

Pete
0
PeterHing
Asked:
PeterHing
  • 3
  • 3
1 Solution
 
aletjollyCommented:
Hello,
Kindly give me a brief description about the topology you are having:
I mean how many sites?
How many servers in each site and what are their roles?
What are the authentication enabled on OWA in each site?
0
 
PeterHingAuthor Commented:
Hi aletjolly - Thanks for your reply:

6 AD Sites, only 2 with exchange installed (US & UK).
1 Exchange server in US and UK each running 3 roles (CAS, Hub and Mailbox)
Authentication is forms-based (Username Only) for both
0
 
aletjollyCommented:
There should be an attribute for the OWAVirtualDirectory viz "ExternalURL", kindly telll me are they pointing to the respected external URLs of the siteand not internal URL
0
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!

 
PeterHingAuthor Commented:
Yes - the URLs on the US box are all correct and say
"https://usowa.mydomain.com"

We have an internal DNS record that allows the URL to be resolved internally, hence why they are both the same.

Points to 400
0
 
aletjollyCommented:
Peter, I believe the URL should "https://usowa.mydomain.com/owa"
Also I am not sure what exactly you mean by "Points to 400"
0
 
PeterHingAuthor Commented:
That was it - thank you. The URL was missing the /OWA in exchange. The reason I couldn't see it working was because when you make the change in exchange - you have to wait for AD to replicate the changes across all sites (15 / 20 minutes).

Points to 400 mean the question was originally set at 300, but because the question was getting longer - I increased them.

Thanks again!
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now