Answered by:
Cannot Connect Outlook 2013 to Exchange 2013

Question
-
Good afternoon,
I recently installed Exchange 2013. I can connect to ECP/OWA via a web browser without any issues - inside and externally. I have successfully created a pop connector and mail is flowing from my test gmail account through the connector in to Exchange. I can also successfully send and receive email - and the external recipient gets the email. Lastly, I can connect to the exchange server from my phone, and all those features work.
What I can't seem to do is get Outlook 2013 to connect to the exchange server - and it is driving me insane! I have used a brand new test laptop with a fresh copy of Outlook 2013 on it - to rule out any pre-existing profile issues. I open Outlook and it auto-completes the server name (in my case the server's name is Exchange), and it autofills in my username. I then get a couple SSL prompts about the cert not matching the server - I can deal with these later. When it gets to the configuring screen it has a green check next to Establishing Network Connection and Searching for testuser@mydomain.com (not my real info). I then get an alert that says: "The action cannot be completed. The connection to Microsoft is unavailable. Outlook must be online or connected to complete this action."
I then installed Outlook on the actual Exchange server, and it does the exact same thing. I cannot tell you how many installs I have done over the years that were much smoother and pretty much worked the 1st time. What am I missing?
Any help would be greatly appreciated!
- Edited by RandyGJr Friday, February 28, 2014 11:19 PM
Friday, February 28, 2014 11:08 PM
Answers
-
Hello!
Try to run the tests from the following microsoft site https://testconnectivity.microsoft.com/ to see which function doesn't have the correct setting. If you need any help please post some logs from the failed tests!
Thank you
Alexios
- Marked as answer by Simon_WuMicrosoft contingent staff Sunday, March 16, 2014 3:58 AM
Saturday, March 1, 2014 2:09 AM -
Thanks for getting back to me. I figured out what I was doing wrong. I was trying to connect to exchange via the old way - servername.domain.local instead of how Outlook 2013 and Exchange 2013 now talk (using GUID and email address). All users can now connect to Exchange via outlook, android, iphone, and OWA.
I figured out that if you use *.domain.com as accepted email it causes issues with iphone. You don't get the message and it says it cannot be downloaded from the server.
I should also mention I had to setup autodiscover on our externally host DNS.- Edited by RandyGJr Monday, March 3, 2014 11:16 PM
- Proposed as answer by Winnie LiangMicrosoft contingent staff Thursday, March 6, 2014 1:11 AM
- Marked as answer by Simon_WuMicrosoft contingent staff Sunday, March 16, 2014 3:58 AM
Monday, March 3, 2014 10:01 PM
All replies
-
Hello!
Try to run the tests from the following microsoft site https://testconnectivity.microsoft.com/ to see which function doesn't have the correct setting. If you need any help please post some logs from the failed tests!
Thank you
Alexios
- Marked as answer by Simon_WuMicrosoft contingent staff Sunday, March 16, 2014 3:58 AM
Saturday, March 1, 2014 2:09 AM -
Thanks for getting back to me. I figured out what I was doing wrong. I was trying to connect to exchange via the old way - servername.domain.local instead of how Outlook 2013 and Exchange 2013 now talk (using GUID and email address). All users can now connect to Exchange via outlook, android, iphone, and OWA.
I figured out that if you use *.domain.com as accepted email it causes issues with iphone. You don't get the message and it says it cannot be downloaded from the server.
I should also mention I had to setup autodiscover on our externally host DNS.- Edited by RandyGJr Monday, March 3, 2014 11:16 PM
- Proposed as answer by Winnie LiangMicrosoft contingent staff Thursday, March 6, 2014 1:11 AM
- Marked as answer by Simon_WuMicrosoft contingent staff Sunday, March 16, 2014 3:58 AM
Monday, March 3, 2014 10:01 PM -