TF400324: Team Foundation services are not availab

Question

When I open my existing solution in Visual Studio 2012 professional, I got the above error. This used to work but something messed up after the computer is rebuilt.

I have installed Visual Studio 2015 Community and can connect to the same collection correctly.

I also tried to use a browser to connect to the same collection. It works fine also.
Cleaning all files in AppData\Local\Microsoft\Team Foundation\4.0\Cache does not work.
It should not be a firewall or proxy issue since Visual Studio 2015 works.
Anyone knows what is wrong with Visual Studio 2012 and how to fix it?

Edit:

This error can happen with later versions of TFS:

Team Foundation Error

TF400324: Team Foundation services are not available from server TFSServer\DefaultCollection.

Technical information (for administrator):

Unable to connect to the remote server

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx.xxx.xxx.xxx:443

Answer 1

In my case, my company VPN my Host machine was connected to was preventing me to access the tfs on a VirtualBox VM, returning this exact error message.

Answer 2

We solved it by adding a specific exclusion to ESET / Kaspersky AntiVirus for the devenv.exe "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe"

Its been working great ever since.

I get basic idea from this link

Answer 3

This error is usually related to the TFS cache. Before you clear the cache folder, please make sure you have closed all instances of Visual Studio and also try to open Task Manager and check if any TFS Services are running. Select each of them and click on End Process Tree.

And also clear the server cache Server cache, the path like C:\ProgramData\Microsoft\Team Foundation\Web Access

Then restart Visual Studio and run as Administrator Mode.

More details you can refer this blog and also could try the better fix.

Note: Make sure you are working on a different workspace rather then VS2015's.