Hi

You resolve one issue but another rears it's ugly head.

Ok...so I had a problem with outlook 2013 connecting onto exchange 2013.

When connecting it came up with an error message for the SSL cert that it was not correct. Reason being is that the domain ip address points to our webserver and not the email server. So the autodiscover was screwed.

Got round this problem by following https://acbrownit.wordpress.com/2012/12/20/internal-dns-and-exchange-autodiscover/

and creating an srv record for autodiscover.

Now the clients are able to create the profile with out the ssl error but it comes up with the error that outlook can not start or open the outlook window. that exchange is not avaiable and either it is due to network problems or the exchange server is down, which is not the case.

Your certificate needs not only Autodiscover but the connection address for all services.

Hi
I do not know what kind of strategy you have chosen for the names of Exchange 2013.
The simplest and most frequently used.
External names, the type of records in DNS A or AAA
OWA, AS, IMAP, POP3, SMTP: mail.domain.com
Autodiscover: autodiscover.domain.com

Internal names, the type of record in the DNS A or AAA
OWA, AS, IMAP, POP3, SMTP: mail.domain.com
Autodiscover: autodiscover.domain.com

Namespace Planning in Exchange 2013 or Understanding Client Access Server Namespaces

Digital certificates and SSL Exchange 2013

Managing Certificates in Exchange Server 2013

Hi,

According to your description, I understand that there is a connection issue when connecting to Exchange account in Outlook. Please confirm whether the issue happens to all users or just specific users.

If the issue happens to all users, please do the following steps to check your Autodiscover service:

1. In client side, please run Test E-mail AutoConfiguration Tool, and collect the Logs tab and Results tab information:

     Open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.

2. In server side, please run the following command:

Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri

If the issue happens to specific users, please create a new Outlook profile or change a computer to have a try.

Regards,
David