I had enabled schannel debug log and compared access backend website through IE9 and ARR on IIS server.Īn SSL client handshake completed successfully.
net2.0 and 4.0.ģ enable tls1.2 as a default secure protocols in WinHTTP. I didn't ran all complete powershell from, just reference it, and change the following items manually, and didn't change any cipher settings or other settings.Ģ setup SystemDefaultTlsVersions and SchUseStrongCrypto as "1" for. It is sometimes misleading to only have 1 end of the communication. Have you compared the packet trace for ARR and the backend web server.
(It seems ARR is running on Windows 2008 (non-r2)) What OS is running there? Can it receive TLS 1.2? Does it have the correct ciphers/etc? I'm not clear what your backend server is running on. Is there anything in the event viewer security giving clues?Ĭompare a packet trace from TSL 1.0 that works to TLS 1.2 see what full suite of communication ciphers/hashes/etc it is using. (that page is Windows 2008R2 and up.) I would try setting it up with a full array of ciphers, etc first to see it working. Maybe you have used a setting/cipher/etc in the script for an OS that it is not designed for. Your version of Windows is ancient maybe you trying to use a cipher or something that is not in that version. I know there TLS 1.2 added retrospectively and there are fundamental differences with the setup of 20R2 when handling things protocol secure I probably haven't used that version for nearly a decade. This might be a Windows 2008 (not R2) thing. I didn't read you not properly and you seem to be using WinHTTP settings. It is quite long, may I share the rewrite part as below, tell me if you need what part of nfig, thank you!
0 kommentar(er)
