locked
Unable to access OWA Internally RRS feed

  • Question

  • We have an Exchange 2007 Infrastructure. We have 2 Mailbox servers configured as CCR & a Hub/CAS server configured with NLB, an Edge Server & Forefront TMG 2010 for publishing OWA & Exchange ActiveSync externally. We cannot access OWA internally but it is working fine externally. We cannot access it using the FQDN or IP Address. We can access it using the physical server's name but cannot when trying to access it using it NLB name. When we tryin to ping its FQDN or IP Address, it gives request timed out. Any help in addressing this issue would be appreciated.

    Fazal Ur Rehman Shah 


    Sunday, September 2, 2012 7:23 AM

All replies

  • Just one Hub/CAS with NLB?

    If you can't access through NLB, then NLB is probably not working right.  Have you looked at Network Load Balancing Manager?  If you want help with that, then you should post the configuration.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Sunday, September 2, 2012 9:21 PM
  • Attached is the NLB Manager's screenshot.


    Fazal Ur Rehman Shah | Senior Consultant

    Monday, September 3, 2012 5:33 AM
  • Does the FQDN for OWA resolve to an IP address that goes to the NLB port?

    I see that you don't have the CAS ports defined in NLB.  Do you not have a CAS array?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Monday, September 3, 2012 1:20 PM
  • FQDN for OWA does resolve but is "Request timed out". We have a CAS array and the ports are defined in the NLB.


    Fazal Ur Rehman Shah | Senior Consultant

    Tuesday, September 4, 2012 5:24 AM
  • A different NLB?  Normally you would define one NLB cluster and put all the ports in it for both CAS and web services.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Tuesday, September 4, 2012 7:35 PM