Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Exchange 2010 CAS Proxying is not working

Posted on 2015-02-13
4
Medium Priority
?
72 Views
Last Modified: 2016-06-23
We're running two AD sites with Exchange 2010 SP3. One site is Internet facing and the other is not. OWA and Activesync work for mailboxes on the Exchange servers that are Internet facing. OWA and Activesync are not working for mailboxes in the non-Internet facing site. The two AD sites have two different CAS Array names.

The CAS servers in the Internet facing site are actually multi-role servers (Mailbox, Hub Transport, and CAS). The CAS servers in the Internet facing site also use an F5 load balancer.

The CAS servers in the non-Internet facing site are CAS\HT servers only. They are in an NLB cluster because we could not afford an F5 load balancer in the non-Internet facing site.

The external and internal URLs are populated on the Internet facing servers but the external URL is not populated on the non-Internet facing servers. The non-Internet facing servers have the internal URL populated with the hostname of the CAS Array in the non-Internet facing site.

When I use the external URL for OWA and Activesync to access a mailbox in the non-Internet facing site it does not work. However when I use the hostname for the CAS Array in the non-Internet facing site OWA and Activesync work. Any help ore suggestions would be greatly appreciated.
0
Comment
Question by:Bill Benson
  • 2
3 Comments
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40608260
1) Any errors on the CAS in the non-internet facing site
2) what happens if you try to proxy a connection from an external source?
0
 
LVL 1

Author Comment

by:Bill Benson
ID: 40608559
1. Proxying the connection from internal and external sources fail.
2. I don't see any Errors or Critical alerts in the Event Viewer.
3. What I see in the browser when I try to connect is I put in my credentials then I get redirected to the CAS server in the  non-Internet facing site. I put in my credentials again and the screen goes white and never renders OWA. I can connect via Outlook with no issues.
0
 
LVL 1

Accepted Solution

by:
Bill Benson earned 0 total points
ID: 40612512
I fixed it :) I just had to configure Windows Integrated security on the non-Internet Facing servers.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes Top 9 Exchange troubleshooting utilities that every Exchange Administrator should know. Most of the utilities are available free of cost. List of tools that I am going to explain in this article are:   Microsoft Remote Con…
If you try to migrate from Elastix to Issabel, you will face a lot of issues. These problems are inevitable but fortunately, you can fix them. In the guide below, I will explain how I performed the migration while keeping all data and successfully t…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month10 days, 22 hours left to enroll

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question