Autodiscovery, and outlook anywhere client profile configuration RRS feed

  • Question

  • If it try to use autodiscover, it fails.
    Basically, it comes back and asks me to login - I log in.
    It then says "The name could not be resolved. The connection to Exchange is unavailalbe. Outlook must be online..."
    It also has a mailbox window open, which shows the correct exchange server name of : EXCHANGE.domain.local
    The Mailbox is shown as "" (normally i would expect to see the mailbox name here.)

    I cannot get autodiscover to proceed further.
    Tuesday, December 27, 2011 9:13 AM


All replies

  • That is indeed unfortunate.  Let us know how you've configured it, and let us know the complete text of all error, warning and information messages you receive.  You'll get better help if you don't obfuscate your company domain because how you have that configured can matter.  Finally, tell us about the certificate you've installed.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Tuesday, December 27, 2011 4:53 PM
  • Hello,


    Please do a remote connectivity test via t he following link. If there are any issues, it will tell you.



    In addition, here are some known issues when configuring ROH:





    Thursday, December 29, 2011 4:03 AM
  • Hi,

    Are you using Exchange 2010 RTM? and Outlook 2003? This problem occurs because the default Exchange Server 2010 Release to Manufacturing (RTM) configuration requires RPC encryption. However, by default, Microsoft Office Outlook 2003 does not use RPC encryption.

    This problem can also occur if you are using Microsoft Office Outlook 2007 and you disable the Encrypt data between Microsoft Office Outlook and Microsoft Exchange profile setting.

    In Exchange Server 2010 Service Pack 1, the RPC encryption requirement is disabled, by default. Any new Client Access Servers (CAS) deployed in the organization will not require encryption. However, any CAS servers deployed prior to Service Pack 1, or upgraded to Service Pack 1, will retain the existing RPC encryption requirement setting.

    Regards from |
    Thursday, December 29, 2011 4:12 AM
  • Hello,


    Is there any update on this thread?



    Simon Wu

    Exchange Forum Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact


    Friday, December 30, 2011 2:02 AM