Exchange 2003 RPC over HTTPS

sliperypete

Limp Gawd
Joined
Jun 12, 2006
Messages
143
Here is what I have setup

Exchange 2003 Domain Controller
Exchange 2003 Exchange 2003 Mail server
CentOS webserver

I also have a hotbrick 1200/2 firewall with static IP's
I use godaddy for my DNS
I have port 80 and 21 pointing to my webserver in a 1 to 1 nat setup
I have port 25 and 443 going to my mail server


I am trying to setup RPC over HTTPS so I can get my mail when I am at school with outlook. I have OWA setup right now and it works fine. I have followed this guide for configuring RPC http://www.amset.info/exchange/rpc-http-server.asp

I can get it to work internally but once I try to connect to it externally it says exchange server cannot be found. Any ideas ?
 
Is your GoDaddy account setup to resolve the dns name you used to setup rpc over http in outlook?

For example my internal dns will resolve chaoticexchange but for RPC to work externally i would have to use chaoticexchange.mydomain.com.

Also check both the "On Fast Networks,...." and "On Slow Networks.." options when you do the exchange proxy settings in outlook.
 
Chaotic Master said:
Also check both the "On Fast Networks,...." and "On Slow Networks.." options when you do the exchange proxy settings in outlook.
If you are using a different internal domain name, this will cause problems as Outlook will try to connect to the external name from internal. So, if you have "company.com" for your external zone and "company.local" as your internal, that should remain configured in the default manner.
 
godaddy resloves the address to my IP , Its my mx record and it has an A record for it as well. OWA works with the address so I dont think its that.

I found a doc on how to troubleshoot this and my internal one is connecting over http not https so its not working for me at all.
 
One question...

Do I do the reg edits and click this is a backend server within the exchange manager ??

I have made 2 reg edits, 1 on my DC and 1 on my Mail server.
 
I still cant get this to work. I have gotten a legit cert so that is ruled out but when I test this internally it doesnt connect over https it goes over tcp. Port 443 is fowarded to that server to becuase my OWA works over https. Any suggestions ?? When I connect externally I notice it never finds my domain controller.
 
I can help you with this.

However, it's such a pain in the ass to type out.

First, check here: http://www.msexchange.org

This is the best site for implementing / troubleshooting Exchange. There are about a dozen articles located here for implementing RPC over HTTPS.

Also, you must ensure that you Outlook 2K3 client is configured correctly. If not, it will always attempt to first connect using TCP. You need to turn this option off!!!

RPC over HTTPS can be a pain when configuring a front-end / back-end server setup, especially if you plan to place the front-end server in the DMZ. I have a port-list that you absolutely need to open, if you're interested in configuring it this way... ...this is how I have it configured for my company.
 
Back
Top