Solved

outlook clients can't connect to new exchange 2013

Posted on 2013-12-15
6
4,798 Views
Last Modified: 2013-12-16
We've just migrated from sbs2008 to server 2012 standard and exchange 2013. Exchange 2013 is up and running. OWA access is up. Activesync is working as well, as smartphones are connecting successfully. The problem still left is outlook clients. Curiously enough, mac outlook clients seamlessly made the switch and are sending/receiving. Outlook on windows however is another story. I did read that outlook and exchange 2013 now require an outside ssl cert, no more self signed. We had an external cert already, and I attempted to export/import it and continue to use it. Outlook complains that the server names don't match, so I've submitted a re-key request. I understand that could be part of the dificulty. When I try to connect an outlook client, autodiscover responds and tells me of the certificate issues, but I accept anyways. After entering the username/password, "finding server settings" reports as successful, but then "log on to server", I receive the error "The action cannot be completed. The connection to microsoft exchange is unavailable. Outlook must be online or connected to complete this action." This is repeatable from multiple pc's, outlook 2007, 2010, 2013. So my question, is this solely related to the SSL certificate issue, if at all? How do I discover my connection settings, so as to manually configure outlook, to make sure autodiscover isn't the problem? What is different about the way mac outlook connects that allows it to work so easily?
0
Comment
Question by:sdholden28
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 

Author Comment

by:sdholden28
ID: 39720840
Outlook then prompts for Microsoft Exchange Server and mailbox
For exchange server, it is populated with the below, presumably from autodiscover:
5e5dc123-77a0-4278-83de-e72e9a5fd20e@domain.com

For mailbox:
=SMTP:2013test@domain.com

2013test is a valid mailbox with owa and activesync working.

I obviously don't know, but those addresses do not look right to me. I have followed the self issued method detailed here, outlook can't connect, but to no avail.
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39720996
That is classic Autodiscover not working problems.
If you have a trusted SSL certificate in place then you need to ensure the host name on the trusted certificate resolves internally to Exchange and the URLs are changed within Exchange to match.

I need to write an Exchange 2013 version, but my Exchange 2010 article shows what needs to be done via Powershell.
http://semb.ee/hostnames

Don't try and use a self signed certificate, that will give you nothing but headaches.

Simon.
0
 

Author Comment

by:sdholden28
ID: 39721280
Thanks. I'll have a look. In the meantime, how can I discover the settings for manual outlook config? Simple I'm sure, just never had to do it.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39721784
You can't use manual configuration with Exchange 2013, because each user has a unique end point (the GUID you see) which means it needs to be returned by the Autodiscover system.

Simon.
0
 

Author Comment

by:sdholden28
ID: 39722171
Excellent article on the autodiscover setup. I've got my certificate sorted and outlook clients are connecting easily. Thanks very much for that.

I've got another issue thats popped up I'm trying to sort that I think is related. Iphone/android users. Autodiscover works sometimes, sometimes it doesn't, even on multiple account setup attempts from the same device. I have some users whose email setup verifies on an iphone right from the start, on any device and works well. I have a handful of users who can setup their account, and it gets "verified", but then when you open the mail app, it says cannot connect to serve. IOS version does not seem to matter, and I've done the simple things... remove account, power cycle device, verify username and password with OWA, etc. Any ideas on where I should look? I'm trying to compare the user accounts between working users and non, but I have found any differences yet. Thoughts?
0
 

Author Comment

by:sdholden28
ID: 39723146
Thanks again for the tip on the dns. This link has the solution for the ActiveSync issues. http://eightwone.com/2011/08/31/exchange-activesync-and-inheritable-permissions-issue/
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you irritated by repeating emails issue in Microsoft Outlook 2016 after recent update ?  Lets’ see how to resolve and prevent duplicate emails in the Outlook 2016 using some simple techniques.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question