Hi guys,

Would appreciate any advise given to the following issue:

I've installed and configured Exchange 2013 Std for a new organization, as a stand alone server.

Very small scale, with all pre and post configuration done. I'm in a testing phase by checking mail flow and set up of accounts from the clients side in outlook, all with success. ( OWA also in working 100%).

Today, when I needed to create their profiles in outlook, authentication takes place until the final step > logging on to mail server, where it fails. I've ruled out any authentication issue that might be the cause.

Regarding certificates, I'm using the self signed certificates exchange creates by default until I receive a 3rd party cert. This also, I believe is still in tact, with no changes made since the initial configuration.

Any ideas as to why there would be a problem logging on to the server all of a sudden?

Note, that accessing their accounts through OWA works perfectly. Just outlook itself where the error occurs.

Thanks in advance

• Edited by Techn101 Tuesday, June 23, 2015 4:01 PM

Hi Corey

I used the tool you mentioned and seems it might have to do with the autodiscover service that giving issues.

Results within the tools shows that outlook anywhere is correct, flagging the autodiscover service as problematic.

I checked my certificates, and there are no indication of autodiscovery whatsoever, might this be the root to the problem or with configuration to the autodiscover service itself?

Regards

I've done a nslookup query on the FQDN of the autodiscover, which returned the incorrect IP ( target ) within the public DNS records, as far as I know it should be created as a CNAME record which points to mail.domain.com.

Or does this CNAME entry point directly to the public IP of exchange?

Hi,

Autodiscover is used to help simplify the configuration of remote Outlook installations and mobile devices to use Exchange. The easiest approach to get over the autodiscover hurdle is to create a public DNS A Record for autodiscover.mydomain.com that points to Exchange public IP address(If you have TMG or SBS, point it to that). This can also be a CNAME alias, but I prefer the A Record.
Meanwhile, "Autodiscover.contoso.com" iteam must be contained in SAN of certificate.

Thanks