![]() The solution was unexpected: all users who reported Outlook start offline problem had Skype for Business (Lync) installed. We reinstalled and repaired Outlook – nothing helped. We tried to delete an Outlook profile and re-create it again.We started Outlook in the Safe Mode ( outlook.exe /safe command) and disabled all Outlook add-ons: the problem persisted.In Exchange 2013/2016, the main protocol for connecting Outlook clients to CAS is HTTPS ( MAPI over HTTP), so it suffices to check the availability of port TCP/443 You can do it using the Test-NetConnection cmdlet: tnc ber-msgcas –port 135 – the port is available. In Exchange 2010, you need to check the CAS server availability from the user computer thought port TCP/135 (RPC locator). ![]() ![]() The accessibility of a mailbox through the OWA interface: the mailbox was available.
0 Comments
Leave a Reply. |