TFS 2010 - 管理员对“/tfs”的访问被拒绝
我正在尝试设置 TFS2010(带有 SP1)服务器,但我一直遇到障碍。
最新版本阻止我做任何有用的事情,因为对“https://tfs.myserver.com/tfs”的每个 HTTP 请求都会导致 HTTP 401。这些请求来自 TFS 管理控制台还是来自 Web 并不重要- 浏览器。每次系统提示我进行身份验证时,我都会输入域管理员的完全限定用户名和密码,但总是收到此错误消息:
Team Foundation Server
TF30063: You are not authorized to access https://tfs.myserver.com/tfs. - The remote erver returned an error: (401) Unauthorized.
管理控制台中只有少数设置有效(例如“更改 URL”),但其他设置(例如“组”)有效。成员资格”(在应用程序层节点上或在团队项目集合上)会导致相同的提示然后失败。
SSL 证书有效,并且 URL 看起来一致。我想不出我错过了什么。
编辑:通常的事件日志中没有任何相关内容。安全日志确实显示了我的审核失败,但我不明白它们,因为我正确输入了用户名和密码(与我用于通过 RDP 访问服务器的用户名和密码完全相同):
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: Administrator
Account Domain: DOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
I'm trying to set up a TFS2010 (with SP1) server and I keep running into hurdles.
The latest prevents me from doing anything useful as every HTTP request to "https://tfs.myserver.com/tfs" results in a HTTP 401. It doesn't matter if these requests come from the TFS Administration Console or from a web-browser. Every time I'm prompted to authenticate I enter the domain Administrator's fully-qualified username and password and I always get this error message:
Team Foundation Server
TF30063: You are not authorized to access https://tfs.myserver.com/tfs. - The remote erver returned an error: (401) Unauthorized.
Only a few settings in the Administration Console work (such as "Change URLs") but others, like "Group Membership" (either on the Application Tier node or on a Team Project Collection) results in the same prompt-then-fail.
The SSL certificate is valid, and the URLs seem consistent. I can't think what I'm missing out on.
EDIT: There is nothing relevant in the usual Event Logs. The Security log does show my Audit Failures, but I don't understand them because I'm entering the usernames and passwords correctly (the very same I use to access the servers over RDP):
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: Administrator
Account Domain: DOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
团体会员资格和团体会员资格有何不同?安全对话框是通过客户端 API 并通过 IIS 进行访问。所有其他内容(例如更改服务器 URL)都会通过服务器模型直接到达数据库。这意味着 IIS 由于某种原因无法在您的域上进行身份验证...
从描述来看,它似乎是一台加入域的计算机。 IIS 是否有权访问域控制器? (它是否连接到域网络)向导会验证您是否可以访问 AD,但如果您随后断开连接...如果 IIS 无法访问 AD,它将无法进行身份验证。 TFS 依赖 IIS 进行 Windows 身份验证。看来它不能这样做。
其他一些要尝试的事情:
What's different about Group Membership & security dialogs is they go through the client APIs and access via IIS. All others such as change server urls go through the server model straight to the DBs. That means IIS cannot authenticate on your domain for some reason ...
From the description, it seems like a domain joined machine. Does IIS have access to the domain controllers? (is it connected to the domain network) The wizards verify you can reach AD but if you disconnect afterwards ... If IIS can't reach AD it will not be able to authenticate. TFS relies on IIS for windows authentication. It appears it can't do that.
Some other things to try:
在尝试了人们提出的有用建议但没有取得任何进展而感到沮丧之后,我决定重新开始并再试一次。我完全卸载了 TFS、SQL Server 和 SharePoint 服务,然后从头开始重新安装。
这次效果很好——无需干预安全性,系统开箱即用。
回想起来,我认为问题在于我使用 SharePoint 的高级选项设置了 TFS,然后我可能摆弄了一些我不熟悉的设置,最终得到了一些东西。
未来的自己请注意:在生产环境中部署之前先在虚拟机中进行练习。
After growing frustrated with trying the helpful suggestions people made but not getting anywhere I decided to start-over and try again. I completely uninstalled TFS, SQL Server, and SharePoint services and reinstalled from scratch.
This time it worked fine - no meddling with security was necessary and the system just worked out-of-the-box.
Looking back, I think the problem was that I set-up TFS with the advanced option to use SharePoint, and then I probably fiddled around with settings I wasn't familar with and ended up making a hash of things.
Note to future self: practice in a VM before deploying in production.