Em Client won't connect to Exchange

I am unable to find the answer. Please post the answer or a link.

Em Client support/help is very non-existent. Like everyone else, I rely on google to help me navigate to the correct page. When I typed the subject line into google, there was no help at all.  My company has security locked down pretty hard. But I’m sure I just need to go in and fix some settings in Em Client for Em Client to be able to talk to the Exchange server.

What errors are you getting? You will find those in Menu > Tools > Operations, and the details will be in the Log tab.

I am having this issue on Mac only. Windows connects and works as expected.
Mac shows an authentication problem of sorts, but don’t understand why. I’ve tried all forms of username (domain\username, username@domain.local, username@internet_domain.com, etc), and all result in the same error.

1:50:30 PM MailClient.Accounts.ConnectionException: Error: SecureChannelFailure (Authentication failed, see inner exception.) —> System.Net.WebException: Error: SecureChannelFailure (Authentication failed, see inner exception.) —> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. —> Mono.Security.Interface.TlsException: Unknown Secure Transport error Negotiation'. 1:50:30 PM&nbsp;&nbsp; at Mono.AppleTls.AppleTlsContext.CheckStatusAndThrow (Mono.AppleTls.SslStatus status, Mono.AppleTls.SslStatus[] acceptable) [0x000dc] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at Mono.AppleTls.AppleTlsContext.ProcessHandshake () [0x0002e] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000da] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool) 1:50:30 PM&nbsp;&nbsp; at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000fc] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp;&nbsp; --- End of inner exception stack trace --- 1:50:30 PM&nbsp;&nbsp; at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00262] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x00176] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp;&nbsp; --- End of inner exception stack trace --- 1:50:30 PM&nbsp;&nbsp; at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x0021a] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00141] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at System.Net.WebOperation.Run () [0x0009a] in \<4b9a7f543fd447a3be5e54f34ee219b2\>:0 1:50:30 PM&nbsp;&nbsp; at System.Net.WebCompletionSource1[T].WaitForCompletion () [0x00094] in <4b9a7f543fd447a3be5e54f34ee219b2>:0
1:50:30 PM   at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <4b9a7f543fd447a3be5e54f34ee219b2>:0
1:50:30 PM   at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute (MailClient.Commands.WorkerStatus status) [0x000fc] in :0
1:50:30 PM — End of inner exception stack trace —
1:50:30 PM at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute (MailClient.Commands.WorkerStatus status) [0x0017e] in :0
1:50:30 PM at MailClient.Commands.Command.Process (MailClient.Commands.WorkerStatus status) [0x00012] in :0


Any ideas?

David

eM Client has some dependencies that are provided by your OS, like .NET, so make sure the OS is fully updated.

There was also an eM Client for Mac update released within the past week. If you have not yet updated, download that from the Mac Release History and see if there is any difference. 

Maybe disable any anti-virus/firewall, VPN etc running on the Mac and then try again.