![]() So I really suspect Outlook for this problem. The Autodiscover CNAME record was successfully retrieved from DNS. ![]() Inbound SMTP mail flow was verified successfully.Īttempting to retrieve Autodiscover CNAME record for domain ''. Testing inbound SMTP mail flow for domain '*** Email address is removed for privacy ***'. Successfully verified specified external domain name settings for your domain in Office 365Īttempting to verify the existence of '' in DNS. You can use this test to confirm that the path that Outlook is taking from your computer to. To verify that Autodiscover is the root cause of this issue, perform an auto-configuration from the affected computer. Testing domain configuration for your domain in Office 365. See Outlook 2016 implementation of Autodiscover to learn more about the full path that Autodiscover takes with Outlook 2016 and later. I used the remote connectivity analyzer which tells me that there are NO problems: However a NEW account on a "clean" Outlook cannot be setup. This happens to both of my O365 domains and worked without a problem in 2013 and after the upgrade from 2013 to 2016 last week. The setup asks my credentials, performs a lookup, asks me for my credentialsĪgain (which previously also happened), but then notifies me that an encrypted connection cannot be setup and an unencrypted connection will be tested, which does not work. After reinstalling my computer (due to a W10 crash) and directly installing Office 2016 (instead of an upgrade), I am facing exactly the same issues.
0 Comments
Leave a Reply. |