Team Foundation Server Setup/Access
Posted
by Angel Brighteyes
on Stack Overflow
See other posts from Stack Overflow
or by Angel Brighteyes
Published on 2010-06-16T12:45:49Z
Indexed on
2010/06/16
12:52 UTC
Read the original article
Hit count: 639
What I need: A TFS 2010 Setup that allows 2 application developers to access the TFS from remote locations.
How it is setup:
- Server 2008 Standard
- 2g Ram
- 300g HD space
- SharePoint Server 2007, using SQL Server 2005
- SQL Server 2008 Standard
- Team Foundation Server 2010
- IIS 7
- Sharepoint Bindings: TFS.DynAccount.Me:80; TFS:80
- TFS Bindings: TFS.DynAccount.Me:8080; TFS:8080
- Using DynDNS service to account for the dynamic ip address being used, this is a requirement for the moment until I can get a better isp package.
Access using Local Accounts
Server is not setup on a domain, or as a domain.
Consequently I did not setup AD services.
Problem:
When logged into TFS using my credentials TFS\AdminUser through the DynDNS account TFS.DynAccount.Me I recieve the 'Red X of Death' on the Documents and Reports folder.
When logged into the TFS through the local peer to peer network using the same credentials TFS\AdminUser I do not receive the 'Red X of Death' problem.
Further Troubleshooting:
When users 'Right Click' the 'TeamProject1' >> Click 'Show Project Portal' it tries to take them to http://TFS:8080 instead of http://TFS.DynAccount.Me:8080, which doing further research I am assuming that it is because team foundation server was setup with a local name of TFS instead of 'TFS.DynAccount.Me' as specified here in Visual Studio Magazines: The Red X of Death.
Users can Access the Team Portal for SharePoint via http://TFS.DynAccount.Me/TeamCollection/TeamProject so it is not like we are dead in the water or anything. However, as most employees/staff are prone to do, they have expressed a great distaste for having to do it this way and just be patient until the current project is finished since we are under a very strict deadline.
Is there a way to set this up differently, or change some settings someplace, reinstall it, point a CName record for our domain website to the DynAccount (e.g. TFS.OurDomain.com points to TFS.DynAccount.Me, which consequently does allow access to the http site without issues), or something. I really don't feel like after all the time and effort I have spent into, first the cost, second the bloody install, third learning SharePoint well enough, fourth the hours into days spent on this, fifth more troubleshooting, sixth employee headaches to just let it lay where it is at.
I figure in my spare/off time I would keep trying to get this to work. So I really appreciate any help any one can give me. I know this is probably something really stupid simple that I will 'Face Palm' over, but at the moment the stress and frustration just has me beat.
Thank you again, this community has always been a great help.
© Stack Overflow or respective owner