答案：并为我所说的话。问题是所有的职位对这一问题进行了相关的旧的Kerberos和IIS的地方代理凭据或AllowNTLM性能进行帮助的问题。我的情况是不同的。我从地上捡蠕虫小时后发现是有些IIS安装不包括协商提供商下的IIS Windows身份验证提供程序列表。因此，我不得不添加和向上移动。我的WCF服务开始如预期进行身份验证。下面是截图它应该如何看，如果你的使用匿名身份验证关闭Windows身份验证

THE ANSWER: And as I have said. The problem was all of the posts for such an issue were related to older kerberos and IIS issues where proxy credentials or AllowNTLM properties were helping. My case was different. What I have discovered after hours of picking worms from the ground was that somewhat IIS installation did not include Negotiate provider under IIS Windows authentication providers list. So I had to add it and move up. My WCF service started to authenticate as expected. Here is the screenshot how it should look if you are using Windows authentication with Anonymous auth OFF.

您需要右键单击Windows身份验证和选择供应商的菜单项。

You need to right click on Windows authentication and choose providers menu item.

希望这有助于节省一些时间。

Hope this helps to save some time.