OWA Display Problems when accessing via Front End Server


I have a niggling (I'm assuming permissions based) issue with regard to accessing OWA via the Front End Exchange server.

7 Exchange Servers (All 2003 SP2)
1 Front End Server (2003 SP2, but virtualised)
SSL Encryption on Front End Server only.

When accessing OWA internally from one of the 7 Exchange Mailbox servers, via http://myserver/exchange everything is displayed as should be.

When accessing OWA internally via the Front End Server https://frontendserver/exchange OR
accessing OWA externally via the Front End Server https://owa.mydomain.com/exchange

I get the attached display.  

This isn't related to a similar behavior where enabling "anonymous access" would resolve as anonymous access is enabled on the ExchWeb directory.

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.

Am pretty sure this is a service pack/patch issue, we had somthingsimilar and had to update the front end to the same as the backend.

Yes, if the FE server is at a lower patch level than the BE, then the proxied response from the BE will contain references to supporting files that don't exist on the FE.  Look at the numbered folders under C:\Program Files\Exchange\exchweb on the BE, and copy to the FE any that are absent.

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
sbearneAuthor Commented:
That did the trick.  Is there a more "best practices" approach to doing this over than copying the cab files over?  I think I used the same copy of Exch SP2 for all servers, but still this problem occurred?

Yes, you must always apply the same hotfixes (many have appeared since SP2) to the FE as well as the BE.
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 Server OS

From novice to tech pro — start learning today.