The XML file was different from the one I had originally only by a version number in the text. Go figure. Thanks for the additional workaround info. It would be nice if someone, perhaps from Microsoft, had actually been able to come up with an answer for you. I am having the same issue, obviously. I am pretty sure it is a firewall issue but I am still working on how to properly configure the rules. I don't have a lot experience there yet.
I found this blog post from a while ago. If you are still experiencing the issue perhaps it will help. Office Office Exchange Server. Not an IT pro? Internet Explorer TechCenter. Sign in. United States English. Stoelting Jan 9, at UTC. Do you have a Firewall? AceOfSpades This person is a verified professional. Firewall with outgoing filtering can cause this. Review your rules. Eric Mar 2, at UTC. It was a firewall policy causing the problem. Thank you for your input!!
I uninstall the workstation anti virus and still having the problem Eric wrote: It was a firewall policy causing the problem. Eric Aug 31, at UTC. A set of manual steps is described in this content through which enterprises can setup Office in Outlook or below versions. Sometimes a situation occurs in which the domain hosting firm is unable to configure autodiscover records of CNAME.
This restricts the domain to properly utilize auto configuration feature provided in Microsoft Outlook. Either Autodiscover records are not setup properly up to the mark or might not be working well due to some unknown reason; whatever it is now you have to manually configure Outlook to connect to Office This means that the manual procedure illustrated in this blog does not apply in this edition of Microsoft Office.
The below-mentioned instructions give guidance to the readers to setup your Office Exchange Online account with Outlook :.
0コメント