I've got two (2) Exchange 2003 servers that host our email for our domain.
On the first Exchange box, I am able to connect people to the server on the LAN, as well as via HTTPS with those users who are more remote. iPhone users are able to connect this email server without difficultly. The public name of the server is the same as the local domain name of the server. This machine is called exchange.ourdomain.com
So, our public domain name, ourdomain.com, happens to also be the local windows domain name, ourdomain.com -- I didn't set this up, but this is the way it is.
The second Exchange box, also on the same LAN, has a name exchangesrv.ourdomain.com. I am able to connect users to this server on the LAN, but am having trouble connecting them via HTTPS for those who are remote and want to still use Outlook 2007 or 2010. iPhone users are able to connect this email server without difficultly, as well.
The server has a DIFFERENT public name (but forwarded to the correct IP address) than the local domain name. So, this second server uses, let's say, exchangesrv.ourotherdomain.com, which forward to the IP address necessary. Again, iPhones can connect and do Active Sync with no problem. But not users in Outlook.
This second server has an SSL certificate that appears to be working just fine, but for whatever reason, when I attempt to add the Exchange users's email account in Outlook using Connect using my LAN options, etc.
Any ideas why this might not be working? My head is spinning trying to figure this thing out.