I am running TFS in Single Server mode (ATDT on 1 machine) and am using the Workgroup edition that came with my MSDN license. Everything works great when connecting from VS Team Explorer on the server.
I can't seem to connect with Team Explorer from my workstation machine. I am trying to connect over the internet, not local LAN.
Can someone please point me in the right direction.
thanks,
Chris
Chris,
You can try configuring IIS to use basic authentication. For more information, please refer to this MSDN article.
Regards,
Jim [MSFT]
Jim I have tried Basic Authentication and receive the same results. I have read in several places that this first version of TFS does not support Basic Authentication; they were not able to get it working and didn't have time to fix up the bugs.
You are correct. TFS over the internet is not supported in V1. We do hope to have this scenario supported in the next release or earlier.
Thanks,
I now have a VPN connection to a private network that my server is on. I can access the web serice URLs through IE but when I try to add the server to Team Explorer in Visual Studio I receive a TF31002 error.
This is my second post after I have followed the documentation and setup a VPN. The first post "disappeared" mysteriously.
Can someone please help me get this to work over the VPN. This is driving me nuts.
Thank you,
Chris
Help with TFS please!
Is there anyway to get REAL Microsoft support with this? This is the workgroup edition that I have with my MSDN license.
The issue is that when Team Explorer connects to the TFS infrastructure it is told the address of the server(s) to communicate with which is a local hostname, not a fully qualified domain name, which would be necessary. You may also need to add custom headers to IIS. I am putting together a blog post on how to do access a TFS server over a WAN. You can see my latest post on the http header information at http://blogs.msdn.com/brianreisman. Please note that this is an unsupported scenario and poses should only be done in a safe environment (eg Not over the internet)
Please note you will need to open up ports 80 and 8080 to work with existing TFS projects. If you will be adding or managing projects you will need to open up your SharePoint administrative port which is certainly not recommended. Also in order to authenticate you will need to use basic authentication (Which means that your login information is going across the WAN in clear text. If you are planning on connecting to TFS over an untrusted network you should use SSL so that the communication is encrypted.
You can make it work by making some manual hacks to your database and adding some aliases to the naming resolution of your internal network. Make sure that you backup your databases and any other settings that you modify so that you can return it to a supported scenario after the experiment.
DO NOT PERFORM THIS UNSUPPORTED HACK ON PRODUCTION SYSTEMS.
Run the following code on your data tier in the TfsIntegration database, replace <NEW_SERVER_NAME> with the WAN fqdn of the application tier computer. (eg. tfs.joltcoder.local)
Declare @OldName varchar(255)
Declare @NewName varchar(255)
select @OldName = url from tbl_service_interface where [name] = 'DataSourceServer'
set @NewName = <NEW_SERVER_NAME>
update tbl_service_interface
set url = replace(url,@OldName, @NewName)
Where url like '%'+@OldName+'%'
--SELECT [name], url, replace(url,@OldName, @NewName)
--FROM tbl_service_interface
--Where url like '%'+@OldName+'%'
If you still are having problems please contact me through my blog and I will do my best to help you.
|brianReisman
TFS Deployment Technology Group
