Re: use RPC over HTTPs with an CNAME
- From: "Mark Arnold [MVP]" <mark@xxxxxxxx>
- Date: Mon, 15 May 2006 11:29:33 +0100
On Mon, 15 May 2006 03:20:01 -0700, Jonathan Chan <Jonathan
Chan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We have setup both backend and frontend server under an internal domain
prefix (test.local) with also enabled RPC over HTTPs. ISA also setup complete
with publishing rules for RPC over HTTPs.
For user easy to remember when setup their outlook, we create an CNAME
record in the external DNS (test.com) which point to the backend server (e.g.
exchange.test.com --> backend01.test.local)
No problem on user to setup their outlook profile (use exchange.test.com and
check names) even no problem when change setting use RPC over HTTPs inside
office.
But when user outside the office and try to setup their outlook profile
(also use exhcnage.test.com and check names). There will have a connection
error unless they change the mailbox server name to backend01.test.local
Do anyone have this kind of experience and can help on this? Many thanks.
You're approaching this from the wrong direction in your head.
What does your certificate say? That's what you need to use. All you
need to do then is to create an A record in DNS to point to the
appropriate IP address (you haven't said whether you're using public
IP on the server or port forwarding on the proxy/firewall etc. etc)
You don't need to worry about Canonicals or anything. The mailbox
server when you set it up is the actual mailbox server and the proxy
server in the Outlook setup is the proxy. Just accept the two are
different (which they almost certainly will be separate boxes) and
move on.
.
- Prev by Date: Re: Disaster Recovery
- Next by Date: Re: Public Folders
- Previous by thread: Re: Schedule+ free/busy connector problem
- Next by thread: Re: use RPC over HTTPs with an CNAME
- Index(es):
Relevant Pages
|
