Rawns Posted July 2, 2018 Posted July 2, 2018 Has anyone else come across the bellow issue when trying to set up an Office 365 account in Outlook 2016 at a site with an Exa connection where Quantum is enabled? We only get this at sites where Outlook 2016 is used and Quantum filtering is enabled (Outlook 2010 does work). We've had a few schools now with this and more to come no doubt. A colleague has reported it to Exa but we've not seen much progress with addressing the issue.
achedgy Posted July 2, 2018 Posted July 2, 2018 I've seen this a few times, randomly on the client, disable ip6, run the wizard to connect and it then connects fine. Once profile created, you can put ip6 back on 1
Rawns Posted July 2, 2018 Author Posted July 2, 2018 Thanks for the pointer. Fairly sure IPv6 is disabled, but I'll double check just in case.
round2it Posted July 2, 2018 Posted July 2, 2018 I am going to move to office 365 over the summer, and I was thinking about having ssl inspection disabled for office 365 traffic as im sure this would slow things down if enabled
DJ-1701 Posted July 2, 2018 Posted July 2, 2018 I am going to move to office 365 over the summer, and I was thinking about having ssl inspection disabled for office 365 traffic as im sure this would slow things down if enabled SSL Inspection is disabled for the vast majority of Office 365 sites on Exa Quantum filtering.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now