Q: How can I determine if my Team Foundation failure is due to a domain naming problem?
A: As mentioned in this post, having a NETBIOS domain name that is not the same as the domain component (DC) of the distinguished name can cause Group Security Services to fail due to a disjoint namespace. To determine if this is causing your Team Foundation install to fail, do the following on the application tier computer:
1. At the Command Prompt, type SET USERDOMAIN and press ENTER. This will return the NETBIOS name of your domain.
2. Install the Windows Support Tools (suptools.msi) found in the \support\tools folder of the Windows Server 2003 installation CD.
3. Click Start, point to All Programs, point to Windows Support Tools, and then click Command Prompt.
4. At the Command Prompt, type ADSIEDIT.MSC and press ENTER.
5. On the Action menu, click Connect To. The Connection Settings dialog box appears.
6. In the Select a well known Naming Context list, click RootDSE, and then click OK.
Note If RootDSE is not listed, there may be a problem with your Active Directory installation.
7. Expand the RootDSE connection node.
8. Right-click the RootDSE folder and then click Properties. The RootDSE Properties dialog box appears.
9. Compare the value of defaultNamingContext with the NETBIOS domain name you obtained in step 1. If the first DC item (e.g., NewYork in "DC=NewYork,DC=corp,DC=fabrikam,DC=com") in the defaultNamingContext value is not the same as the NETBIOS domain name, this will cause Group Security Services to fail.
For more information, see Domain Controller's Domain Name System Suffix Does Not Match Domain Name.
Applicability: Visual Studio 2005 Beta 1 Refresh with Visual Studio 2005 Team System