Office 365 Keeps Disconnecting To Outlook 2016 For Mac
Best free mac apps for video games. Open MS Outlook 2016. In MS Outlook, select the Tools tab and click Accounts. In the Accounts dialog box, click the plus sign in the bottom left corner and select Exchange. Sep 26, 2016 - since we installed windows 10 and office 2016.outlook keeps disconnecting from exchange server.they need to reopen or relog. 9 replies.
By SSL Bridging I only mean re-encrypting on the trip to the real servers so adding ‘ssl verify none’ will make it SSL Bridging. I’m glad ‘option accept-invalid-http-request’ fixed your problem, HAproxy follows RFC’s and drops non standard HTTP traffic by default unless you tell it not to, you could have verfied this was happening by using the stats page and a socat command to see errors: echo 'show errors' socat unix-connect:/var/run/haproxy.stat stdio More info here: Obviously Microsoft have been getting better However, I’d still double check you are not seeing “req” errors on your state page and that: echo 'show errors' socat unix-connect:/var/run/haproxy.stat stdio Shows no errors either. I too often end up raising the client / server timeout’s which in the past(Again mostly Exch 2010) I’ve needed to raise up to 45 mins or more, it may be worth a try as a test if nothing else. Alright, I did some tests. Adding the option accept-invalid-http-request didn’t work, I’m still getting disconnected.
(Assuming this command should be put in the frontend fe_ex2013 section. And does it matter in which order?) echo “show errors” socat unix-connect:/var/run/haproxy.stat stdio shows Total events captured on [04/May/2018:08:25:45.536]: 0 Playing with client / server timeouts had no effect either. Btw, what do you mean by “However, I’d still double check you are not seeing “req” errors on your state page”? I’m assuming you’re not talking about the stats page, as I’ve not seen any error messages on that page (My version is: HA-Proxy version 1.5.18 2016/05/10). Jiggz: Another thing I just noticed is that HAProxy is ignoring my “maxconn” command. On the stats page it shows session limit 2000 for all the frontends and 200 for all the backends. Because you didn’t configure a maxconn value for the frontend, so it defaults to 2000.
There is no real backend maxconn (relevant to this configuration) and you also did not specify any maxconn values for the servers. Maxconn in the global section sets the per process maxconn value. Frontend and server maxconn are distinct values with there own defaults. Somewhere in (the middle?) there I got disconnected, and I then reconnected myself by pressing “send/recieve” all folders. Actually I noticed that this method works every time for “manually” connecting myself after a disconnect. Needless to say, not an ideal method. Another thing that got me thinking.
I’m using the hosts-file for “fake dns” at the moment. Otherwise I can’t test HAP in production (Zen is up 'n running in production right now).
I’ve just added autodiscover and the exchange namespace to the hostfile. Is this approach acceptable for testing or could there be something “leaking” over from the current LB (Zen).
Something cached? I’ll again point out that Windows is happy testing HAP this way (editing the hosts file). I’ve read somewhere that emptying the cache on the Mac Outlook could fix some problems. Well, I tried that.
BUT now, a short while after emptying the cache, I’m having even worse problems Now I can’t even connect to Exchange anymore, Outlook just asks for credentials at startup (which it didn’t before I emptied the cache). Then, even though I enter the correct credentials, I can’t connect. I just get an error message stating “Mail could not be received at this time”. The server for account xxxxx returned an error. Logon failure: unknown username or bad password. Your username/password or security settings may be incorrect. Would you like to try re-entering your password?'
Needless to say, re-entering won’t work. (Neither the trick with empying the keychain). Now I’m even more confused.
Just to add to why I’m fussing about timeout’s a little, I’ve worked with a lot of Exchange and HAProxy deployments and I’ve always found I need longer timeout’s than those seen in configs online. System preferences mac keyboard shortcut for app. After my last post I did a google search to see if my theory of 45-60m timeout’s are justifiable and this guy certainly thinks so: Hi Everybody!
I wanted to post some steps that might save you some time and money. Although all of the below settings are published on Microsoft somewhere, they aren't all together or always specifically called out to assist in creating a more. I tried extending both server and client timeout values to 30min. It had no effect though And no, no errors on the stats page. In fact there have never been any errors visible there (Yep, unfortunately I had already looked at the article you provided). The current situation is a little bit different now.