locked
Outlook 2013 cant connect to Exchange 2013 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a simple domain in my home to support using TFS

    I recently restaged my entire setup to Windows 8 and Windows Server 2012

    I was introducing Exchange 2013 to the environment

    I went through a standard install, everything looked like it worked

    I was able to create mailboxes for the domain administrator and me

    I tried connecting to the exchange server as me using outlook 2013

    In setting up the profile, it almost instantly recognizes me

    However, it sits and spins forever trying to connect to the server and finally gives up

    I looked at the host name in the profile, and it has something very guid like in the profile instead of the name of my exchange server

    How does that guid get translated to a connection?

    Im wondering if something went wrong in my AD setup

    There's not much in the exchange section of the AD on the primary domain controller

    How does one verify that the setup is correct?

    This is a totally 2012 server / Windows 8 client domain.

    Monday, December 10, 2012 5:09 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I looked at the host name in the profile, and it has something very guid like in the profile instead of the name of my exchange server

    How does that guid get translated to a connection?

    Hi,
    Michael Van Horenbeek has written a very good blog post about the new Client Access Architecture where he explains why there is a GUID shown where we used to see the name of a CAS Array when having Exchange 2010 or the actual Mailbox Server in earlier versions.

    See: A closer look at the changes in the Client Access Infrastructure in Exchange Server 2013


    What's important to understand is that RPC Access is not longer available when connecting to a mailbox in Exchange 2013. Outlook will only connect with Outlook Anywhere and for that to work, you need to have a certificate installed that your clients trusts. If that is not the case, Outlook will not connect.

    See Step 4: Configure Mail Flow and Client Access


    Martina Miskovic

    Monday, December 10, 2012 6:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    All i had to do was create an active directory certificate server on a virtual server

    I turned on the web enrollment facilities, and the problem cured itself

    exchange requested a certificate on its own, and the clients can now connect


    Thursday, December 13, 2012 6:44 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    This type of issue has come in previous Exchange-Outlook config also. The cas array turned the name to Instance -GUID. Microsoft has gave fix at that time. This time..I think, we need an input from Microsoft itself

    Regards from ExchangeOnline

    Monday, December 10, 2012 5:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I also see this in my deployment. For example, my Exchange 2013 server FQDN is mail.contoso.com.

    If I use mail.contoso.com when configuring Outlook 2013 Mailboxes for users in AD, the name failse to resolve like ScottBerger describes above.

    If I locate the <big_long_unruly_number_like_a_GUID>@contoso.com, and paste that into the Exchange server name field, it resolves just fine, and the mailbox for the user is setup and works fine.

    I wonder if this might be the issue in my inability to get Site Mailbox to work in SharePoint 2013?

    Stu

    Monday, December 10, 2012 5:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I looked at the host name in the profile, and it has something very guid like in the profile instead of the name of my exchange server

    How does that guid get translated to a connection?

    Hi,
    Michael Van Horenbeek has written a very good blog post about the new Client Access Architecture where he explains why there is a GUID shown where we used to see the name of a CAS Array when having Exchange 2010 or the actual Mailbox Server in earlier versions.

    See: A closer look at the changes in the Client Access Infrastructure in Exchange Server 2013


    What's important to understand is that RPC Access is not longer available when connecting to a mailbox in Exchange 2013. Outlook will only connect with Outlook Anywhere and for that to work, you need to have a certificate installed that your clients trusts. If that is not the case, Outlook will not connect.

    See Step 4: Configure Mail Flow and Client Access


    Martina Miskovic

    Monday, December 10, 2012 6:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    All i had to do was create an active directory certificate server on a virtual server

    I turned on the web enrollment facilities, and the problem cured itself

    exchange requested a certificate on its own, and the clients can now connect


    Thursday, December 13, 2012 6:44 PM