According to the results from Microsoft's Remote Connectivity Analyzer, there is a problem with your autodiscover service, which is the service used by Outlook to automatically locate your Exchange server.
Autodiscover is a web service running on your Exchange server, and it should be published to the Internet just like OWA and all other Exchange web services (EWS, ECP, OAB, ActiveSync); an Outlook client will try to locate it using three systems:
- It will look for a web server at the URL
https://yoursmtpdomain.com and, if one is found, it will call the web service from this site.
- If this fails, it will try the same with the URL
- Finally, if this fails too, it will look for a DNS SRV record called
_autodiscover._tcp.yoursmtpdomain.com and connect to the web server pointed to by that record, whatever its actual name is.
Neither of these solutions seem to be in place in your environment, thus the autodiscover process fails, and Outlook doesn't know where it should connect to. There actually is a web server answering at the URL https://jonesstuckey.com, but:
- It's not your Exchange server
- It doesn't have a valid certificate, because the site name doesn't match the certificate name.
I took the liberty to do a quick probe to your Exchange server, which I (correctly) guessed is located at https://mail.jonesstuckey.com. The certificate you're using contains the names
www.mail.jonesstuckey.com (which looks useless), so, unless you want to replace it with another certificate containing also
autodiscover.jonesstuckey.com (which would be the correct solution), you can only successfully use the third autodiscover method, i.e. create a DNS SRV record called
_autodiscover._tcp.jonesstuckey.com and point it to
mail.jonesstuckey.com on TCP port 443.
This should fix your autodiscover problem; if then your Outlook clients still can't connect, post another question and we'll see if we can help you further.