This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.
We have collected Fiddler logs from machine on which the connection was succesfull and from one problematic one. After the investigation from RnD they have found that the TLS 1.0 was disabled on the problematic machine and on the working one was enabled. So, after enabling the TLS 1.0 on the problematic machines the problem was fixed.
Steps how to anble TLS 1.0:
- Browse to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
- Right click on the Protocols folder and select New and then Key from the drop-down menu. This will create new folder. Rename this folder to TLS 1.1 or TLS 1.2 (depending on the protocol you want to enable)
- Right click on the TLS 1.1 or TLS 1.2 key and add a new key underneath it.
- Rename the new key as: Client
- Right click on the Client key and select New and then DWORD (32-bit) Value from the drop-down list.
- Rename the DWORD to DisabledByDefault.
- Right-click the name DisabledByDefault and select Modify... from the drop-down menu.
- Ensure that the Value data field is set to 0 and the Base is Hexadecimal. Click on OK.
- Create another DWORD for the Client key as you did in Step 7.
- Rename this second DWORD to Enabled.
- Right-click the name Enabled and select Modify... from the drop-down menu.
- Ensure that the Value data field is set to 1 and the Base is Hexadecimal. Click on OK.
- Reboot the server