ApplicationPoolIdentity无法访问网络资源 [英] ApplicationPoolIdentity cannot access network resources

问题描述

我的设置:W2K8-R2 IIS7.5 x64位服务器(尽管应用程序池以32位运行)

My Setup: W2K8-R2 IIS7.5 x64bit servers (app pool is running in 32bit, though)

我们有一个(.net 4.0)Web应用程序，该应用程序在"ApplicationPoolIdentity"下运行.它启用了"Windows身份验证".该Web应用程序在不同的(旧的-W2K3 II6)Web服务器(相同的域)上调用Web服务.该Web服务也需要Windows身份验证.

We have a (.net 4.0) web application that runs under the "ApplicationPoolIdentity". It has "Windows Authentication" enabled. The web app calls a web service on different (older - W2K3 II6) web server (same domain). The web service requires Windows Authentication as well.

在我们的某些Web服务器上，它运行良好，并且我可以看到Web App调用了Web服务并将其自身标识为正在运行的Web服务器的机器名称(如预期的那样).但是，在其他Web服务器上，该应用程序在调用Web服务时将无法标识自己，因此会收到403错误(这可以通过查看Web服务的IIS日志来确认).

On some of our web servers, this works well and I can see that the Web App calls the web service and identifies itself as the machine name for the web server it is running on (as expected). However on other web servers the application will not identify itself when it calls the web service and thus gets a 403 error (this is confirmed by looking at the IIS logs for the web service).

我已经将可以正常工作的Web服务器与不能正常工作的Web服务器进行了比较，我找不到任何明显的不同. (我比较了两个站点的ApplicationHost.Config文件，除了几个加密密钥以外，它们是相同的.)

I've compared the web servers that work versus those that don't and I can't find any significant differences. (I compared the ApplicationHost.Config files from both sites and with the exception of a few encryption keys they are identical).

是否有任何想法导致坏机上的应用程序池标识放弃标识自己?我们是否在一台Web服务器上设置了某些内容，而在另一台Web服务器上错过了它?

Any thoughts on what could be causing the App Pool Identity on the bad machines to forgo identifying itself? Did we set something up on one web server and miss it on the other?

如果没有，有人可以推荐可用于跟踪正在发生的事情的工具吗?

If not, can someone recommend tools that could be used to track down what's going on?

感谢您的帮助.

推荐答案

一个更新，以防万一有人遇到此问题...我们意识到，工作的服务器之间的共同点是最近重新启动了它们.重新启动问题服务器后，它们也开始工作.

An update in case anyone runs into this... We realized that the common thread between servers that worked was that they had been rebooted recently. After rebooting the problem servers, they too started working.

在这一点上，我无法解释问题所在，但似乎重新启动即可解决.如果问题再次出现，我将进行更新.

At this point I can't explain what the issue was, but it appears a reboot solved it. I will update if the problem reoccurs.

这篇关于ApplicationPoolIdentity无法访问网络资源的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！