kmcnet
Guest
|
Posted:
Tue Dec 21, 2004 9:07 pm Post subject:
Outlook HTTP over RPC |
|
|
Hello Everyone and thanks for your help in advance. I am setting up Outlook
2003 to access Exchange 2003 over HTTP/RPC. I have read the following
article:
http://support.microsoft.com/Default.aspx?id=833401
Additionally, I have opened and forwarded port 6001-6004 on the firewall.
However, I am still unable to connect. However, when I try to connect behind
the firewall to the mail server, i.e. mail.mydomain.local, I am able to
successfully connect. I have not made any registry entries since it appears
that the article says they are set up by default. Also, since I can connect
locally with RPC, then I would think the mail server is listening on the
appropriate ports. So I am really not sure what the problem is or where to
being troubleshooting. Any help on this issue would be greatly appreciated.
Thanks.
|
|
neo [mvp outlook]
Guest
|
Posted:
Wed Dec 22, 2004 3:08 am Post subject:
Re: Outlook HTTP over RPC |
|
|
Since the article mentions single server setup, here are some tips to watch
out for.
1) Only port 443 (HTTPS) needs to be open on the firewall to the Exchange
server
2) The desktop client must have a copy of the root CA installed (public
half) (If Outlook 2003 can't trace the web server certificate back to the
signing CA, it fails the connection and throws no error messages. So if
running an internal CA and issuing your own certificates, make sure the
desktop gets a copy of your internal root CA certificate.)
3) If you have SP1 applied to Exchange 2003, you no longer have to expose
the GCs in the RPC Proxy registry keys. Exchange 2003 SP1 has a change
where it proxies the calls. (The registry key for the RPC Proxy only needs
to be the Exchange server for port 593, 6001-6002, and 6004.)
4) If running Exchange 2003 SP1, go to the server object in ESM. Bring up
the properties and go to the RPC-HTTP tab. Make sure you specify that the
server is a back-end server.
Lets see what else... there is a registry key called DisableRpcTcpFallback*
that you should use. Many that claim to have it working find that it isn't.
(Start Outlook with the /rpcdiag switch to confirm the connection is HTTP
and not TCP/IP.)
Best advise I can give, get the feature working internally first before
venturing to test from the Internet. Once you get it nailed from an
internal location, externals just fall right into place. If you need a
rough idea on what the client configuration,
http://www.msexchange.org/tutorials/outlookrpchttp.html is pretty good (the
dialogs have changed slightly).
Outside of that, Microsoft has a whitepaper for RPC/HTTP deployment at
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/ex2k3rpc.mspx.
It has been updated for Exchange 2003 SP1. I've found this paper very
helpful in first time setups.
/neo
* HKCU\Software\Microsoft\Office\11.0\Outlook\RPC\
DWORD = DisableRpcTcpFallback
Value = 1
"kmcnet" <kmcnet@discussions.microsoft.com> wrote in message
news:F071AEC6-50A2-4170-AA79-3B1E26194652@microsoft.com...
| Quote: | Hello Everyone and thanks for your help in advance. I am setting up
Outlook
2003 to access Exchange 2003 over HTTP/RPC. I have read the following
article:
http://support.microsoft.com/Default.aspx?id=833401
Additionally, I have opened and forwarded port 6001-6004 on the firewall.
However, I am still unable to connect. However, when I try to connect
behind
the firewall to the mail server, i.e. mail.mydomain.local, I am able to
successfully connect. I have not made any registry entries since it
appears
that the article says they are set up by default. Also, since I can
connect
locally with RPC, then I would think the mail server is listening on the
appropriate ports. So I am really not sure what the problem is or where
to
being troubleshooting. Any help on this issue would be greatly
appreciated.
Thanks.
|
|
|