Tuesday, February 20, 2007 4:28 AM bart

Team Foundation Server and fully qualified domain names

For the moment, I'm responsible to set up a TFS machine for a team project that's performed over the internet. No big deal you might think? Well, there are some issues that you have to beware of.

The most 'difficult' one is the "fully qualified domain name" issue. When you install TFS, quite a bunch of references to the machine are kept as the NETBIOS name (e.g. TFSLAB01). These references are used by lots of services (e.g. a page called tfsredirect.aspx will use a registry setting to gather reports in the SharePoint environment) as well as the Team Explorer clients (for which settings are obtained via and exported through a web service call to the TFS machine).

As you can imagine, the server naming above does work out for intranet scenarios but on the internet a name like TFSLAB01 is worthless. There are a few solutions to this:

  • Have every team member connect to the company over VPN.
  • Modify the hosts file on each team member's dev box by adding an entry that points TFSLAB01 (the TFS server name) to the right IP.
  • Change some settings on the TFS machine to use the FQDN. Read Mike Glaser's blog entry for more information.

Have fun!

Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Filed under:


# re: Team Foundation Server and fully qualified domain names

Tuesday, February 20, 2007 5:44 AM by Fredrik

We use the VPN solution, and it works like a charm :)