I am having trouble with external Outlook 2010 clients connecting to Exchange 2010. I ran the connectivity tests, and the autodiscover service is not working externally. Unlike previous RPC over HTTPS clients where I could manually type in the server name, nothing fixes this problem. Meanwhile, OWA and ActiveSync work just fine. How do you configure your Windows 2008 R2 with Exchange 2010 (single) server with one certificate so it works on the Internet? There is no "autodiscover.domain.com" as this would require a second IP address. Thanks for any help.

actually you need to publish A Record "autodiscover.yourdomain.com" but point it to your current IP (no need fro a seconed one). Regarding the certificate, you need to buy a UCC (unified communication certificate) which is especially for exchange 2007 / 2010. This certificate actually include up to 5 names and you need it to publish all internal and external names of your server including autodiscover.domain.com: mail mail.domain.local mail.domain.com autodiscover.domain.com autodiscover.domain.local you need to publish those records (the external one's) and point it to your external IP.Yanir Ben-Nun / System Team Leader / IT / IS Professional

Thank you...I tried this over the weekend but the Exchange connectivity test site said autodiscover failed. I should add that internally my DNS is on Windows Server 2008 R2, but externally it is maintained by ZoneEdit. I went to Godaddy and purchased a UCC certificate, but when Outlook loaded it complained that the CN for autodiscover.domain.com did not match.

Hi, Could you post the testing information of Exchange connectivity site on the form? how did you set the external name of Outlook Anywhere? Please ensure the external name to be same as CN value (autodiscover.domain.com) of the certificate. After that, please check this issue. Thanks Allen

Thanks, your suggestions helped to fix the problem. I did need a UCC certificate, but there was also an IIS issue which needed to be fixed. I am happy to say everything is working correctly now.