Outlook 2016: Office365 connection "Disconnected" - which ports or protocols to open on Proxy Appliance?
Hi,
We make use of Office 2016 as well as Microsoft Office 365 ("Exchange Online").
When connecting Outlook with a direct (open / unrestricted) internet connection it is able to connect to Office365's online Exchange Servers, but the moment the Computer accesses the internet through our Forcepoint Websense Proxy Appliance it shows "Disconnected". The specific user and PC does have full inrestricted http (tcp/80) and https (tcp/443) access.
Obviously Outlook makes use of a different protocol or port (AutoDiscover?) and it is not able to establish this connection, almost like it is not using a protocol over http or https.
Users making use of Outlook 2013 does not have the same issue, so it must be something to do with the way that Outlook 2016 makes the connection to the online Exchange Servers of Microsoft.
Any pointers on what needs to be opened / allowed on our Proxy Appliance or how Outlook 2016 connects to Exchange online?
Thanks,
Reinhard
We make use of Office 2016 as well as Microsoft Office 365 ("Exchange Online").
When connecting Outlook with a direct (open / unrestricted) internet connection it is able to connect to Office365's online Exchange Servers, but the moment the Computer accesses the internet through our Forcepoint Websense Proxy Appliance it shows "Disconnected". The specific user and PC does have full inrestricted http (tcp/80) and https (tcp/443) access.
Obviously Outlook makes use of a different protocol or port (AutoDiscover?) and it is not able to establish this connection, almost like it is not using a protocol over http or https.
Users making use of Outlook 2013 does not have the same issue, so it must be something to do with the way that Outlook 2016 makes the connection to the online Exchange Servers of Microsoft.
Any pointers on what needs to be opened / allowed on our Proxy Appliance or how Outlook 2016 connects to Exchange online?
Thanks,
Reinhard
Alex
Put a bypass in for those addresses
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a lot guys, your articles helped me in the right direction. I had to add an exception on our Proxy Appliance Content Gateway not to intercept and decrypt https traffic going to the URLs and IPs in the articles (add "incident", and "tunnel" the traffic on Websense Content Gateway) after which the connection went from "Disconnected" to "Connected".