I will cover details of further troubleshooting in second part of this article.
#MAC MAIL EXCHANGE SERVER NOT RESPONDING FOR MAC#
It did, however, failed to address the issue for Mac Mail client! No eureka moment, just yet! But if that was the issue, why did Outlook for Mac work without any errors?Īnyhow, I proceeded changing the 100-continue handling by changing it from default setting of RFC-2616 compliant, to RFC-7231 compliant instead:Īfter changing this setting, I ran the EWS test from exrca website again, and as one would expect, the test passed with no issues. It would be easy to blame load balancer at this point and implement the recommended fix by changing 100-continue handling on LoadMaster. The issue is also documented by Brian Reid: Exchange Web Services (EWS) and 501 Error and Phil Sharp: Kemp Load Balancer and Lync Unified Contact Store Integration Note.Īfter enabling L7 debug tracing on my KEMP LoadMaster I observed the same error mentioned in the above articles “lb100 kernel: L7: badrequest-client_read (-501): 
The error is somewhat misleading as when you look at EWS logs on Exchange server, you will see that the server responded to the request with HTTP error 400 which translates to “bad request”. Mac Mail was throwing “Account Error” which read “Unable to connect … The server returned error: Connections to host on default ports failed.”
#MAC MAIL EXCHANGE SERVER NOT RESPONDING PC#
It is worth pointing out that while Outlook 2013/2016 on PC use MAPI/HTTP or RPC/HTTP to connect to Exchange 2013/2016 servers, both clients on Mac (Mac‘s own Mail client and Microsoft Outlook for Mac) uses Exchange Web Services (EWS). If Method 1 doesn't resolve the problem, and you're not using a custom domain together with Office 365, you can use the Add New Account Wizard in Outlook to set up your Outlook profile by using the default ''-based email address that's associated with users' Exchange Online mailboxes when you signed up for Office 365. Latest Microsoft Outlook for Mac did not exhibit any issues either! Microsoft Outlook 2013/2016 clients on PC did not exhibit any issues. The connections to the Exchange servers were also encrypted. KEMP LoadMaster was configured to terminate SSL connection on the load balancer. The Exchange environment was mixed Exchange 2013 and Exchange 2016 but load balancer was configured to use only Exchange 2016 servers. The load balancer was configured to user Layer 7 load balancing. On his Mac, built-in Mail client would not connect to Exchange through KEMP LoadMaster. My good friend and renowned Exchange MVP Jeff Guillet ( fame) brought an interesting issue to my attention.
0 kommentar(er)
