hank you for your reply.
I saw that article before I posted. I don't quite understand what it wants
me to do.
"Requests for /exchange on the CAS are proxied to /exchange on the BE
server, which returns the OWA 2003 experience "
THIS IS NOT WHAT I SEE HAPPENING. It returns 'Page can not be displayed',
not the OWA 2003 experience. NOTE- my CAS server also has the HUB/Transport
role. Is that the problem?
DNS has entries for orange.domain.net and gold.domain.net
http://gold.domain.net/exchange works fine - brings up 2003 OWA (there is no
cert on this server). I want to be able to use
https://orange.domain.net/exchange to access a 2003 mailbox as the article
says I can, but instead I get "page could not be displayed".
For this to work:
What changes do I need to make in DNS?
What changes do I need to make in IIS?
What changes do I need to make in Exchange?
Quote from the article,
1 Exchange 2007 CAS-only server
1 Exchange 2003 BE server
All mailboxes on the BE server
Requests for /owa returns the following error since there are no Exchange
Outlook Web Access could not find a mailbox for DOMAIN\USER. If the problem
continues, contact technical support for your organization and tell them the
following: The mailbox may be stored on a Microsoft Exchange 2000 or
Microsoft Exchange 2003 server, or the Active Directory user account was
created recently and has not yet replicated to the Active Directory site
where this Client Access server is hosted.
Requests for /exchange on the CAS are proxied to /exchange on the BE server,
which returns the OWA 2003 experience
Requests for /public on the CAS are proxied to /public on the BE server,
which returns the OWA 2003 PF experience
Requests for /exchweb: exprox either proxies them to /exchange or /public on
the Mailbox server, or does nothing with them
Uh, I think it's doing nothing.
"Leif Pedersen [MVP]" wrote: