We have set up Network Load Balancing (NLB) on two Hub Transport/Client Access servers.(Windows Server 2008/Exchange Server 2007)When we go directly to either of the nodes, we can access OWA just fine.However, when we try to go to the new NLB cluster, by name or IP address, we get this: The page cannot be displayed The page you are looking for is currently unavailable.The NLB cluster name and IP are in DNS; nslookup works fine and we can ping it by name and IP address.What am I missing?We have followed several articles to the letter. They all have the same information and do not indicate the need for any additional configuration once the cluster is set up. Is there any configuration needed in IIS for this?

Clarify: Users cannot access OWA via NLB cluster, either FQDN or IP address, right? Troubleshooting: 1. Does there have other issues among users? AutoDiscover and Mail Flow 2. Those NICs are not teamed NICs in NLB, right? please see KB 278431 3. Do both CAS/HT FQDN and NLB virtual FQDN belong to same domain suffix? E.g CAS/HT FQDN: CASHT.domain.com | NLB FQDN: MAIL.domain.com 4. Can you post Nslookup result here for NLB name from CAS/HT server? 5. Go to IIS, confirm if SSL required is checked for OWA virtual directory 6. Check NLB setup process [Load Balancing Exchange 2007: it includes both CAS/HT configuration] 7. Go to both nodes, check OWA's URL a. EMC->Server Configuration->Client Access b. Outlook Web Access tab->OWAs properties->General tab->whats your internal and external URL? Notes: you may try to change internal URL with NLB cluster name for testing Notes: Please also check application log on both NLB nodes, any related warning or error info would help to do the analysis

Hi, Briggl, I assume your question has been answered, and I'd like to change the status to "Marked as answer", please feel free to post here if you have any update