Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

(team) socket hang up / (team) undefined after switch to Azure VM #288

Closed
evtk opened this issue Jul 17, 2017 · 2 comments
Closed

(team) socket hang up / (team) undefined after switch to Azure VM #288

evtk opened this issue Jul 17, 2017 · 2 comments

Comments

@evtk
Copy link

evtk commented Jul 17, 2017

Hi,

I have been succesfully using the plugin to connect to a TFS 2015 update 2.1. This was on a internal network where I was connecting from a virtual machine to the TFS environment (both internal).

We have now switched to the Azure platform, which is external of course. While making the connection from the Azure VM to our TFS server, I get these errors:

(team) undefined
(team) socket hang up

As far as we know, the firewall has been configured correctly for use of our TFS server. Since I can connect to TFS by simply browsing to the webinterface from my Azure VM.

Are there any specific ports we need to open to be able to use the plugin. Or is any additional configuration needed?

Thanks!

@evtk
Copy link
Author

evtk commented Aug 1, 2017

We haven't booked any progress on this. Is there anyone out here who can help us out or assist us in anyway? Thanks.

@evtk evtk closed this as completed Aug 29, 2017
@guilala
Copy link

guilala commented Nov 22, 2018

I am trying to have azure-repos-vscode login to a custom tfs server. I can enter my domain\user and password, but after that i also get '(team) socket hang up'. Like this, TFS is NOT supported in VS Code. @evtk why did you close this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants