setting up gmail in outlook 2016 server certificate error

#SETTING UP GMAIL IN OUTLOOK 2016 SERVER CERTIFICATE ERROR MANUAL#

I guess my next call is to Stationality to find out why connection tests are trying to resolve to a 69. IP address (which is ) instead of 70. (which is ) Everything is trying to use Autodiscover, which makes no sense since this was all working just fine yesterday before the SSL cert expired. For some reason, when running the Microsoft Connectivity Test, it hits the SSL cert for, which is definitely not the cert it should be finding. is web host company that hosts our public-facing website. I just got off the phone with 'advanced' support from the CA and they have now confirmed that the certificate was created and installed properly (as was the Intermediate). My impression that OP was doing this and was still receiving the error 'unable to connect'īut obviously that isn't a FQDN and therefore not what I used in the cert.

#SETTING UP GMAIL IN OUTLOOK 2016 SERVER CERTIFICATE ERROR MANUAL#

When the screen comes up and says it can't find the server, OP needs to enter manual setup and manually specify the external servername. You may be able to come up with a kludgy autodiscover-type setup with 2003 by configuring a public CNAME which resolves to the IP address of the OWA server, and adding autodiscover as a SAN on the certificate, but it will not work as expected and will probably not be as fluid a process as using the actual autodiscover service available in 2007+. īeing that this is exchange 2003, there is no autodiscover service, no xml file and no autodiscover virtual directory (which the phones are programmed to seek), also likely no autodiscover CNAME or A record - all of which the phones and MS's remote connectivity test service are looking for. Probably why the test is failing, though.

True but I bet the phones are trying to use it to resolve the FQDN of the mail server. > Autodiscover wasn't around until Exchange 2007.

Setting up gmail in outlook 2016 server certificate error