Front End OWA is not redirecting to my internal Exchange 2007 CAS Servers.

I am in the process of launching Exchange 2007 in my company.  We have Exchange 2003 and are in Native Mode.  We have an Exchange 2003 OWA Server that routes fine to all the 2003 Exchange Serversbehind it (3 of them).  I installed 3 new Exchange 2007 Servers and 1 New OWA CAS Server that points to the outside.
I can access one of my internal Exchange Server with the CAS role on it fine.  However I cannot access the others 2.  I get Event ID 41 on the OWA CAS Server as described below.  The test email account in  this message was created on a new Exchange 2007 Server through the console as recommened.
Event ID: 41
The Client Access server "https://BLANK.BLANK.com/owa" attempted to proxy Outlook Web Access traffic for mailbox "/o=BLANK, Inc/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Email Account ". This failed because no Client Access server with an Outlook Web Access virtual directory configured for Kerberos authentication could be found in the Active Directory site of the mailbox. The simplest way to configure an Outlook Web Access virtual directory for Kerberos authentication is to set it to use Integrated Windows authentication by using the Set-OwaVirtualDirectory cmdlet in the Exchange Management Shell, or by using the Exchange Management Console. If you already have a Client Access server deployed in the target Active Directory site with an Outlook Web Access virtual directory configured for Kerberos authentication, the proxying Client Access server may not be finding that target Client Access server because it does not have an internalUrl parameter configured. You can configure the internalUrl parameter for the Outlook Web Access virtual directory on the Client Access server in the target Active Directory site by using the Set-OwaVirtualDirectory cmdlet.

In the web browser I get the error below.

Outlook Web Access is not available. If the problem continues, contact technical support for your organization and tell them the following: There is no Microsoft Exchange Client Access server that has the necessary configuration in the Active Directory site where the mailbox is stored.

I've been beating this to death for quite some time.  I'm not an expert at IIS, but it seems that all roads have lead me to it.
I am using Exchange 2007 with SP1 on all 3 servers.  I installed Rollup 9 on 1 of them to see if this would help out.  The three 2007 Servers have CAS, Mail, and Hub.  The internet facing OWA has CAS.

Any assistance would be apprciatted, as I am at wits end. LOL...

Thanks
copioAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Ahmed ShahbaSystem ArchitectCommented:
fist,its good to divide role,like one server HUB,one CAS,one mailbox,(may be two cluster mailbox and one server with HUB and CAS roles.) anyway>open exchangmanagmentconsole>server configuration>client access server>write on Owa on three server and choose  integrated  authentication  and basic or form based as in your design,then go to internalurl &externalurl and define them. (do all by clicking each server)restart IIS in the three server by run IISreset in command prompt .
0
copioAuthor Commented:
That didn't work.  I did as you said and when I would enter the Domain credentials I would get an OWA Window that said "To get better performance use this url".  The url was the internet link and that went on in a loop.  I tried to get in internally and go the same results.  I set everything back to how it was and I was able to get into OWA internally, inside the LAN, but not via the internet, except to the one Exchange Server I mentioned above.
0
Ahmed ShahbaSystem ArchitectCommented:
why you keep front end serves since you have cas server.?
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

copioAuthor Commented:
Maybe I am using the wrong terminolgy, not sure.  The 3 Exchange Servers with Mail, need to be accessed internally, so we use the internal link via https.  There is 1 external CAS that we would like to use to view mail via the internet via https as well to route to any of the 3 servers on the inside.  Hope I am not confusing.  Thanks.
0
Ahmed ShahbaSystem ArchitectCommented:
I think you may read this article for proxy and redirect CAS

http://technet.microsoft.com/en-us/library/bb310763.aspx
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
copioAuthor Commented:
I read the link, thank you ahmed.  I'm still experiencing the same issue.  I am using Exchange 2007 SP1.  I can get to the US mail server behind the CAS Server, but not the other 2 mail servers.  This is driving me nuts!  LOL  Would installing SP2 help?  I'm grabbing at straws at this point.  Thanks.
0
copioAuthor Commented:
Not a complete answer.  I needed to do a lot of research to figure this one out.
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 Applications

From novice to tech pro — start learning today.