Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...

In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...

Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:

Exchange Server: 32857e39-d12d-4adf-b4b9-83822442a3db@mydomain.net

Mailbox: =SMTP:richard@mydomain.net

When I fill in the right fields....it won't connect and falls back to the values above...

Something wrong in the Exchange setup?

April 28th, 2015 3:16pm

The failure to connect isn't because of what you're describing, those values look normal.
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2015 5:19pm

Hmm...the only else I see is a popup message before, that it complains regarding a wrong certificate on the proxy server and therefore it can't connect...

Though it is just a plain installation with the self-signed certificates generated by Exchange 2013 SP1...

Could this be the problem?

April 29th, 2015 2:13am

Yes.  Obtain proper certificates trusted by your clients.  If you're going to connect mobile devices, then get a certificate from a trusted third-party provider.  Go Daddy is one of the cheapest.
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2015 3:01am

Is there a good guide how to install the certificates for Exchange 2013 SP1?

So far I've used only StartSSL....the cheapest I've found for Web certificates...though complicated online handling, but allow to have one certificate for several wildcard domains.

April 29th, 2015 3:07am

Hmm...found aguide here:

http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/

Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...

So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

Free Windows Admin Tool Kit Click here and download it now
April 29th, 2015 3:13am

Okay...works now....process of getting certificate from namecheap.com took around 30 minutes (o;

April 29th, 2015 7:39am

Do your users' mobile devices trust those?  I'm always interested in learning thrifty solutions to recommend.
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2015 5:19pm

Do you mean if the mobile devices trust the certificates from namecheap?

I haven't setup the external access completely yet....

May 2nd, 2015 7:08am

Yes, that's what I mean.  I'll look forward to hearing the results.  I'm told that in the very beginning Go Daddy had trust issues with mobile devices, but I've not seen that in any of my customers now for a long time.
Free Windows Admin Tool Kit Click here and download it now
May 2nd, 2015 4:01pm

Hello Ed

Connecting from outside...meaning setting up a new Exchange account on Outlook for Mac on OS X and on a Lumia 830 phone didn't show any certificate errors for namecheap.com.

Also logging in with a web browser for the outside shows no cert errors/warnings....though only tested on Safari on OS X though...

May 4th, 2015 5:47am

That's good to know.  Thanks for getting back.
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2015 12:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics