Annoying Outlook Anywhere

Hi All

Having recently published our Exchange 2010 SP2 CAS Array to host Outlook Anywhere, via NTLM, I'm about to throw them across the room !

We have this scenario :-

OWA :
Public IP1 - Cisco FW - External IP1 - ISA 2006 Listener 1 - OWA Rule - Internal IP - Cisco FW NAT IP1 - OWA

OA:
Public IP2 - Cisco FW - External IP2 - ISA 2006 Listener 2 - OA Rule - Internal IP - Cisco FW NAT IP2 - CAS

The two published systems run on separate IP's from the internet, all the way through to the Exchange boxes, sharing only the internal IP of the ISA box.
Our OWA uses RSA SecurID, so it has a separate listener on the ISA.
The NAT on the internal Cisco Firewall runs on two sets of different IP's.

Our OWA rule works perfectly. The OA rule doesn't !

When we test OA, traffic is seen on the ISA, coming into the OA External IP, but then a new connection is initiated from the OWA External IP to the NAT IP. The connection sits there until the timeout is reached. We then see an error which correctly states the IP's in the path and says that the "connection attempt failed because the connected party did not properly respond after a period of time".

Does anyone have a step-by-step guide of how and what the ISA settings should be, as well as a method to track traffic beyond the ISA, to see if the OA request is actually reaching the CAS array ?

Thanks in advance
LVL 1
DoveSupportAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
A number of things here.

1. Exchange 2010 SP2 is no longer supported. Went end of life a few months ago, so should be upgraded.
2. You have mentioned the CAS Array. The CAS array is an INTERNAL name only, it should not resolve externally. It is for INTERNAL MAPI traffic only. If you have used the same host name for anything else (OWA, Outlook Anywhere etc) then you will expect problems because the client gets confused.

Simon.
0
DoveSupportAuthor Commented:
Thanks - the upgrade to SP3 is planned.

All of the literature I have seen, tells me to point an OA publishing rule at my CAS address - the logical address of my NLB. The OWA and CAS have different host names, and the CAS array has an entry on the correct DNS servers, so it resolves correctly across the firewalls involved. We do our OWA this way and it is fine.
Are you saying that I need a new DNS entry, specifically for OA, which points to the logical IP of my NLB ?

Any more suggestions regarding the rule setup ?
0
Simon Butler (Sembee)ConsultantCommented:
The CAS address and the CAS array are two different things.
You can use the same IP address, but the DNS entries should be different.
Similarly the CAS Array address does not and should not be on your SSL certificate - it should be used exclusively for the CAS array functionality.

Simon.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

DoveSupportAuthor Commented:
I think you're off on a tangent here. I need to figure out what settings my ISA publishing rule should have, more than worry about my CAS array or IP.

The certificates are ok and my NAT is fine. The problem - as I see it - is the ISA rule.

Has anyone else published OA or ActiveSync under the same setup as we have ?
0
DoveSupportAuthor Commented:
Hi Admin, please could you close this ticket for me, without awarding points ?
Thanks
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DoveSupportAuthor Commented:
Managed to resolve the situation. Reset SSL certificates and reconfigured ISA Listeners. In the end it just started working.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Forefront ISA Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.