防止构建时出现 UNC 共享错误
在工作中，我们的开发服务器上托管着许多网站。 包含所有这些站点的文件夹被映射为网络驱动器。
在 VisualStudio 中，我将网站的根目录作为网站打开，当我构建网站时，我总是会收到此错误。
错误 4 加载配置文件时发生错误：无法开始监视更改 'I:\Sitename\wwwroot\' 因为 网络 BIOS 命令限制已 到达。 欲了解更多信息 错误，请参考微软 知识库文章 810886。 托管 不支持 UNC 共享 Windows XP 平台。 I:\站点名称\wwwroot\web.config
我已查看了知识库文章并对其建议的注册表进行了更改，但这没有帮助。
有谁知道这个问题的修复或解决方法？
谢谢
At work we have a bunch of sites hosted on our development server. The folder containing all these sites is mapped as a network drive.
In VisualStudio I open the root of the site as a WebSite and when I build the site I alwys get this error.
Error 4 An error occurred loading a configuration file: Failed to start monitoring changes to
'I:\Sitename\wwwroot\' because the
network BIOS command limit has been
reached. For more information on this
error, please refer to Microsoft
knowledge base article 810886. Hosting
on a UNC share is not supported for
the Windows XP
Platform. I:\Sitename\wwwroot\web.config
I've checked out the KB article and made the registry changes it suggests but this didn't help.
Does anyone know of a fix or workaround for this?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
不要使用映射驱动器，而是使用完整的 UNC 路径，并为当前登录的用户提供对该路径的访问权限：
\\MachineName\Sitename\wwwroot\web.config您很有可能会获得不同的效果由此，特别是如果映射驱动器正在使用不同的凭据进行映射。
Instead of using a mapped drive, use full UNC path and give your current logged in user access to that path:
\\MachineName\Sitename\wwwroot\web.configChances are high you will get a different effect from that , especially if the Mapped drive was being mapped with different credentials.
查看此修补程序：http://support.microsoft.com/kb/911272
它解决了问题
Take a look at this hotfix: http://support.microsoft.com/kb/911272
It cures the problem
使用该修补程序更改 FCNMode 并不总能解决问题。
我在这里对这个问题做了非常详细的回答： https://stackoverflow.com/a/20710473/705198
这个答案是我能找到的有关该主题的所有 technet、msdn 和博客参考资料的积累，以及我们最终必须采取的措施来解决该问题。 禁用巨型帧（HP 服务器网卡问题导致另一个错误）和 SMB2+ 与注册表编辑相结合，最终使我们的高流量 IIS 站点得到了拯救。 注册表编辑本身只能使网络 BIOS 限制错误在正常负载下不会显示得那么快。
Changing the FCNMode using that hotfix doesn't always fix the problem.
I made a very detailed answer to this problem here: https://stackoverflow.com/a/20710473/705198
That answer is an accumulation of all the technet, msdn, and blog reference material I could find on the subject, and what we ended up having to do to fix the problem. Disabling Jumbo Frames (HP Server NIC problems causing another error) and SMB2+ combined with the registry edits were what ended up saving us with our high traffic IIS sites. The registry edits alone only made it so the network bios limit errors would not show up as fast under normal load.