Do you have Integrated Windows authentication enabled? - check in IIS

Service account meets requirements? See User Accounts Required for Team Foundation Server Setup in the Installation Guide.

Also, check your event logs for other symptoms.

This can be caused by a number of issues.

Some of them are:

1. DNS issues. You are unable to resolve by just the machine name and must use Fully Qualified names.

2. The domain users are on a different domain as the TFS Server, and unless mapped in the host files, it may need fully qualified names

One way around this is to place in your host file the server and IP address. It will resolve locale in case the DNS is having issues.

Okay, I added the machine name to my host file and now that URL comes up with the same error as before (http://awimtfs01:8080/services/v1.0/ServerStatus.asmx):

Error: Access is denied.

And it still doesn't get passed that error...any other ideas? Do i need to start the install from scratch for that to propogate or should clicking try again after I've tested the url do the trick?

Access denied is a different issue.

Basically at this point, you are able to hit the server, but your authentication is being rejected.

Access Denied can come from a number of sources.  If it is coming from IIS, then you will need to make sure that you have NTLM Authetication set on the server.  Since you can access via localhost, and cannot via machine name, you may need to set the NTAutheticationProviders on your site.

c:\inetpub\adminscripts\cscript adsutil.vbs set w3svc/NTAuthenticationProviders "NTLM"

You may need to check the folders underneath w3svc:

adsutil.vbs get w3svc/<siteid>/NTAuthenticationProviders

to make sure they are not set.  You can get the site id from inetmgr by clicking on "Web Sites" and in the right it will list all your sites with the id number for each one.

If the access denied is from team foundation, you will need to make sure that the user has permissions to things like the database (or if it gives you enough info) the folder it needs.  Since this works with localhost, my guess is that this isn't the issue.

Thanks for taking the time to explain this. I can actually access the web service correctly with the machine name as long as I use the domain prefix on it e.g. awimtfs01.domain.com.au:8080, but if I use awintfs01:8080 that is when I get access denied. The authentication pops up for both addresses though. When I put in the TFSSERVICE credentials, it works on the domain prefix one and not the one without. I've tried this a few times and I've cut and paste the same password in for both sites with no difference.

What is confusing me is that I've followed the help to the letter and it's a fresh base install of Windows Server 2003 Standard Ediition but I'm getting this. The help doesn't mention setting up NTLM Authentication etc. to get this to work.

I also checked the database security and it has added TFSSERVICE as a username for all the databases created with role of TFSEXEROLE and some even have dbowner set.

Thanks again for your suggestions...hopefully I can get this up and running with your guys help..

Jeremy

Hmmmm... that is weird.

I am certainly no expert on domains and why fully qualified names work while non-fully qualified name does not. There could be a number of things that we could try to look at.

1. Proxy servers: While I do not think this would play into it, but hey, we never know. My understanding is that sometimes, when accessing a site, you may need to go through a proxy server, and log on to it. Normally, IE Browser does this for you and negotiates all the necessary permissions on it's way to hit the server. You may want to check your proxy server to see if you have any to authenticate. Maybe that is what is sending an access denied.

2. IE Settings: We rely on (not sure if use use directly) various components in IE browser, including proxy settings. My understanding, is that when we have a period (".") in the name, IE assumes by default that it is an internet site, and therefore uses Internet Zone Security. This may include going out to the proxy and authenticating. You can usually tell what zone you are in by checking the icon at the bottom (along with the name next to it) to see if you are in "Internet", "Intranet", "Secure" or "Restricted" zone. I may be wrong, but, it may see the fully qualified name as "Internet" and the regular name as "Intranet". You can try a combination of dropping the fully qualified name into the "Intranet" zone to see if that makes a difference. Also, for proxy settings, you can try the following:
- Uncheck "Auto Detect" for proxy setting (then try again)
- If you have a Proxy Server and it is checked, check the "bypass prxy server for local addresses" (then try again).
These can be found by selecting "Tools" --> "Internet Options..." --> "Connections" --> "Lan Settings..."

3. DNS Issues: I am not familiar with DNS at all, and really am not sure what to suggest here, but it may be resolving only fully qualified names (if that is even an option).

That is great!

Thanks for trying out Visual Studio Team Foundation

Hi Jeremy,

That is correct. That is what you should see when you navigate to http://awimtfs01:8080

Thanks,

Brad

I think I have get the idea,but My English is very poor,I can't read it,and solve it.

I'm a Chinese girl.

Why ?haven't a chinese version?

My God!

Any idea?I cannot but translate it.It is very difficult for me!