H
happouh
Guest
Hello,
We have TFS 2015 for which we are going to force TLS1.2.
We noticed that, when we force the connection to use TLS1.2 on the TFS side, older versions of Visual Studio (at least 2008 and 2013) had issues to connect.
We get the following error message:
TF400324: Team Foundation services are not available from server servername\projectcollectionname. Technical information (for administrator): The request was aborted: Could not create SSL/TLS secure channel.
However, we can get to the server using IE and Chrome from the same machine. We can see that the SSL certificate is valid and that it uses TLS1.2.
Visual Studio 2017 can get to TFS without problem when TLSa.2 is forced.
I added registry keys like I have seen on other place, but have had no luck so far.
Any suggestion would be great.
Thanks all
Continue reading...
We have TFS 2015 for which we are going to force TLS1.2.
We noticed that, when we force the connection to use TLS1.2 on the TFS side, older versions of Visual Studio (at least 2008 and 2013) had issues to connect.
We get the following error message:
TF400324: Team Foundation services are not available from server servername\projectcollectionname. Technical information (for administrator): The request was aborted: Could not create SSL/TLS secure channel.
However, we can get to the server using IE and Chrome from the same machine. We can see that the SSL certificate is valid and that it uses TLS1.2.
Visual Studio 2017 can get to TFS without problem when TLSa.2 is forced.
I added registry keys like I have seen on other place, but have had no luck so far.
Any suggestion would be great.
Thanks all
Continue reading...