![]() We followed this for guidance: įortunately, in our case Windows and Exchange were already well patched so we only needed to add these registry keys and DWORD items on the server and reboot it. This is great solution because only the server needed to be touched and we did not have to touch the workstations. ![]() If you successfully connected to the account before, try to connect to it from another Exchange application, such as Outlook. If there is a problem with the connection, the indicator icon will be orange. Look at the Exchange account in the left pane. This works because Windows 11 supports TLS 1.2 by default at this time and Windows 2008 R2 can be made to support TLS 1.2. Solution: Check your Microsoft Exchange server connection. That is all of the workstations connected to the same subnet as the server never had a problem after the Windows 11 upgrade, but all of the workstations outside of that subnet failed with proxy (Error Code 80000000). I am using MacBook with office Enterprise E3 License, whenever I reconnect my network or connect to new network outlook didnt connect to exchange server automatically I have to restart my outlook every time to connect to exchange server, is there any solution for my issue. In our case, this happened when the Windows 10 workstations were upgraded to Windows 11 and is only noticed on workstations connected outside of the subnet the server is connected to. Issue with Outlook (Office 365) connect to exchange server. Therefore, Outlook can't communicate with Exchange. Our failed configuration was: Outlook 2013 running on Windows 11 not connecting to Exchange 2010 running on Windows 2008 R2 via proxy.Ĭause of failure: Windows 11 disables TLS 1.0 and TLS 1.1 by default and Exchange 2010 running on Windows 2008 R2 uses TLS 1.0.
0 Comments
Leave a Reply. |