New “features” of RPC over HTTPS for Exchange 2003 introduced in SP2

UPDATE
Only the client end when putting in the “exchange server� address you need to put in the local FQDN e.g. mydomain.local even if you are outside the network and it cannot be resolved. THEN you put in the external FQDN in the “connections� tab. Once the connection has been made to the RPC proxy on IIS it then tries to use the information in the “exchange server� field to access the Exchange server.

Information in this article works fine http://support.microsoft.com/kb/833401/en-us

——————————————————–

Microsoft implemented a new security feature (I am assuming) that in order to connect into an RPC Proxy enabled Exchange server from the internet via HTTPS tunnel you first need to create the Outlook profile in house on the clients LAN (or VPN in if possible) where it can talk to the Exchange box on standard RPC (TCP 135) only then will it let you connect in via RPC over HTTPS externally…

Just so you don’t waste 5 ½ hours of your life like I just did.

REFERENCE:
http://thelazyadmin.com/index.php?/archives/299-More-on-RPC-Over-HTTPs.html

“You may not be able to create a new profile or edit an existing profile if client is not on the LAN with access the Exchange Server using RPC via TCP 135. The profile has to be configured to use RPC over HTTP while the client is connected to the internal network and can access the Exchange Server via TCP port 135. If you are using ISA 2004, the publishing rule that was created to allow RPC over HTTPS takes care of this concern, however if you are using a different firewall you need to be aware of this.�

No related posts.