OWA and iPhone exchange is working but Outlook client doesn't resolve my local exchange 2013 server
Exchange 2013 just installed, OWA and iPhone exchange(internally and externally) is working but Outlook 2010 client doesn't resolve my local exchange 2013 server. All Exchange services are running. I can ping the exchange server's name and
it resolves to the correct IP. I really would like to move to Exchange from what we have but it isn't working! Help! I'm really hoping that I just have to flip a switch because I've spent so much time troubleshooting this already!
Thanks for any suggestions...
March 25th, 2013 11:20pm
What error message did you get when you configure your Outlook profile?
Free Windows Admin Tool Kit Click here and download it now
March 26th, 2013 1:39pm
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
March 26th, 2013 8:42pm
Hi Lucas,
Outlook in Exchange 2013 connects via HTTPs, so please check your Outlook Anywhere settings, and make sure the URL can be resolved internally.
Fiona Liao
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2013 12:28pm
Hey Fiona,
Thank you so much for the reply. So since Outlook 2010 can only connect to Server 2013 via outlook anywhere it doesn't really matter what I put in the "Microsoft Exchange server:" location because it should be connecting instead with
the Outlook Anywhere settings. Ok... So I was able to save Outlook Anywhere settings on a mail profile to test and then when I selected that test profile to open up with Outlook 2010 the first thing that pops up is this picture attached below along
with a login window for my credentials that will not take my valid credentials. Something to do with the security certificate. I have an external CA signed certificate that I can't use until we make the cutover to this server so I'm working with
a self-signed certificate. My self signed certificate target sight matches my self-signed cert so do you think this could be the problem? How to I work around this?
Thanks!
Lucas
"There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site "Name of exchange server."
Outlook is unable to connect to the proxy server. (Error Code 10)
March 28th, 2013 9:36pm
So, I finally figured out why it wasn't working in Outlook 2010. You need to have the security trusted in your Trusted Root certificates before you connect. In Outlook 2013, it's better because it gives you the option to view the certificate
and install it.
Resolved!
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2013 4:21pm