Outlook 2003 over rpc/https

[Vit Knyshevich]

Hi,
I cannot get Outlook 2003 using RPC/HTTPS. I performed 833401 completely but
it still tries to open port 135 on Exchange, I've found by netstat. Why it
doesn't even try to open port 443?

Best regards,
Vit Knyshevich.

 

[Vit Knyshevich]

I use single server, as it described in 833401. I mentioned I've performed
833401 completely, so I have RPC/HTTP proxy and certificate installed. I
have reply from https://server/rpc/ as it described in 833401. I have OWA
and OMA working fine. But it doesn't matter because Outlook even doesn't try
to open port 443, although I configured mail profile to use Exchange
connection over rpc/https.

Best regards,
Vit Knyshevich.

 

[Vit Knyshevich]

I was wrong. Actually it tries to connect to port 443, but it disconnects
very quickly. The question is why it cannot establish RPC/HTTPS connection
succsessfully. Something wrong, I still cannot find. I'm litle confused that
the single server has two server names and two ip addresses - internal and
external. OWA, OMA and /rpc/ vfolders are published by ISA publishing rules,
OWA and OMA works fine but rpc/https does not.

Following 833401 I published web server sertificate with external server
name. Also I specified external server name as mail server and as rpcproxy
server in mail profile.

Best regards,
Vit Knyshevich.

 

[Vit Knyshevich]

I've done. That is my success story.
1. I've found some MSFT guy mentioned DWORDisableRpcTcpFallback=1 registry
value in Outlook's RPC registry key. This value prevents RPC over TCP using.
2. I changed mail server name in mail profile from external name to internal
name. So, mail server is internalname.domain, prcproxy server is
externalname.domain. I didn't use mutual authentication. I didn't add
anything to client's HOSTS file to resolve internalname.domain. I used
splitted domain configuration to resolve externalname.domain. If you cannot,
just use HOSTS file. I used company's CA certificate on web-server and I
installed it on client computer.

As I mentioned above, I've performed 833401 completely, and after I set
DisableRpcTcpFallback=1 and changed mail server name in mail profile,
Outlook has connected successfully. I spent a lot of time and I was
rewarded.

I've checked out that configuration on a single server (E2K3SP1+DC/GC+
RpcProxy+ISA2KSP2, SSL listener, /rpc/* is published) and with two boxes
(one box was W2K3+E2K3SP1+DC/GC+RpcProxy behind the second box, second one
was W2KSP4+ISA2KSP2).
Thanks all guys that helped me, I'm happy.

Best regards,
Vit Knyshevich.