Forum Discussion
Office365 connectivity test:
- Jun 13, 2023
Hi CocoKola, could you please help me with the following 3 questions?
1. Is TLS 1.2 protocol disabled on your machine?
M365 connectivity test tool service requires TLS 1.2 to establish SSL connections. You may check that on your registry editor to see if it's disabled. You could search "Registry Editor" in the taskbar and open it, then navigate to the following path:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
TLS 1.2 should be enabled to use M365 Connectivity Test Tool .exe client.
2. Are the following two cipher suite on your machine?TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (
0xc030)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)Cipher suite can also be checked in Registry Editor. The path is:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\CipherSuite
Those two cipher suites are required by the connectivity test tool service.
3. is .NET Desktop Runtime 6 installed on the machine?
This shouldn't be the reason for the SSL connection failure but I see the exception code 0xe0434352 in the crash log you provided in the comment on May 21st, so just want to double-confirm. Is the crash log below from the issue in the original post saying "Unable to connect to origin. Inner exception message: The SSL connection could not be established, see inner exception" shows when executing the rich client?
If the TLS and cipher suites configuration are unknown, you can also try to enable them on the machine using this software or modify the registry through the Registry Editor and see if the issue can be resolved.
The software is NARTAC which can be downloaded from:
https://www.nartac.com/Products/IISCrypto/DownloadNo installation requires. Checking the needed TLS protocol and Cipher Suite should work.
I'm trying to find the root cause of the issue. Could you please help me with the following two questions first?
1. Are you using a proxy to connect to the Internet?
2. Could you please try downloading the standalone connectivity test tool to see if we could get the whole error message? It works quite similarly to the desktop application but in a console.
The standalone rich client could be downloaded here: https://connectivity.office.com/api/AnonymousConnectivityTest/DownloadStandAloneRichClient
After the download is finished you could simply click it and see if the same issue shows up again and if there's more inner error message. There will be consent required after executing the console.
If you run into some problems when using the standalone rich client, here're guidelines for it: https://learn.microsoft.com/en-us/microsoft-365/enterprise/office-365-network-mac-perf-onboarding-tool?view=o365-worldwide#testing-from-the-command-line
or you could comment here.
Thanks.
Downloading the tool I have the same issue, nothing happens. I had seen previously the downloaded app crashed with that pop-up.
I tried launching the direct link above but running as admin and this time I was prompted for permission to run on what looked like a PowerShell terminal pop-up and goes away.
- kenipotterJun 16, 2023
Microsoft
Hi CoCoKola, can you try dingxin's latest comments? It maybe the TLS version and Cipher suites problem in the client-side operation system settings.
Appreciate if you can have a try and provide more feedback. So that we can provide more support.
Thanks~ - CoCoKolaJun 12, 2023Copper ContributorMissed this post until now... Yes 'DigiCert Global Root G2' is listed and is active.
2. yes it is still having the same issue and the same results.
I clicked "best response" by mistake. ID10T
I unchecked it right away, but I guess the automated message still goes.. 😉 - dingxinJun 12, 2023
Microsoft
Thanks. Could you please help me clarify the following two questions?
1. Is 'DigiCert Global Root G2' on the operating system's trusted issuer list, as described in the private message I sent to you? There should be some trusted issuers on the list for the client to trust the certs received from servers.
2. Could you still repro this issue? I'm asking this question because I received an email saying you marked the answer "Browser's trusted issuer list might be different from the operating system. I've sent a message to check the information" as an accepted solution. - CoCoKolaJun 10, 2023Copper Contributor
dingxin I identified this as the issue by looking up the error code for this thread, plus I have checked and tested every other possibility. I checked certs from what I know and didn't set anything obvious.it's it guaranteed?no.
It was the same error code in the log file generated by this connectivity app. Look up the 0x8.. Error from original post the the log file from the stand alone app you provided. You will find what I found.
- dingxinJun 08, 2023
Microsoft
Could you please provide more information about the error message? what's the cert and time issue? - dingxinJun 06, 2023
Microsoft
Browser's trusted issuer list might be different from the operating system. I've sent a message to check the information. Thanks.