Issues with connecting to the Server 2008 R2 website often stem from network or configuration challenges.
Issues with connecting to the Server 2008 R2 website often stem from network or configuration challenges.
Hello, I’m dealing with a tricky issue on my older Windows Server 2008 R2 setup. We can’t reach certain websites using HTTPS (like yahoo, tk.de, datev.de, etc.) even though the connection works fine otherwise. The problem occurs across five different systems, and none of them have deep packet inspection. All servers are up-to-date, except for a patch gap between this month and January. The TLS handshake is functioning correctly, but connections drop when the site files load. Everyone I know uses DigiCert certificates. Do you have any insight into what might be causing this? It’s been frustrating for a week now.
It's notable that I receive TLS 1.2 from Google but only TLS 1.0 from Yahoo, along with the client hello. The expected behavior is TLSv1.2 since you configured the tls_min setting in Firefox to the correct value "3".