Hi guys, we are facing a strange problem for one of our client locations. We have a server in 1 country but clients from 4 other countries/sites. Since last week our clients from London have the following problem:
[
Problems connecting to the TFS server at using Visual Studio 2013. I am getting the following error:
TF205020: Could not connect to server 'http://******:8080/tfs/defaultcollection'. This server was used in your last session, but it might be offline or unreachable. Confirm that the server is available on the network. To attempt to connect again, or to a different
server, click 'Connect To Team Foundation Server' in Team Explorer or the Team menu.
The server returned the following error: TF400324: Team Foundation services are not available from server http://*******:8080/tfs/defaultcollection.
Technical information (for administrator):
The request was aborted: The request was canceled.
When I try to access TFS site at http://******:8080/tfs, it works fine after I entered in my credentials.
I have removed the TFS server from my Visual Studio settings and tried adding it again without success.
Here are the other things I have tried without success:
1) Deleting the TFS cache at C:\Users\****\AppData\Local\Microsoft\Team Foundation\5.0
2) Removing the TFS token storage from the registry at HKEY_CURRENT_USER\Software\Microsoft\VSCommon\12.0\ClientServices\TokenStorage
3) Clearing and deleting Internet Explorer cache and cookies
4) I have also added the following setting to the devenv.exe.config:
<defaultProxy useDefaultCredentials="true" enabled="true">
<proxy usesystemdefault="true" />
</defaultProxy>
5) And the following reconmendation
<defaultProxy enabled="true" useDefaultCredentials="true">
<proxy bypassonlocal="true" proxyaddress="http://*****/"/>
<bypasslist>
<add address="*******"/>
</bypasslist>
</defaultProxy>
None of the above steps I have taken have solved this connection issue.
]
We have at least one proxy between our server and the remote site.
We can see that a lot of the requests from VS2013 are receiving a 401, before being retied with proper credentials.
If we add Fiddler on the client side acting as a second proxy, then VS2013 can work. (This is how we got the info on 401 results above)On the server side all looks good for that user, except the same big amount of 401 errors.
Any help will be welcome.
