Hi, I had a ASP.NET 1.1 web project on a share of a remote server and I could
compile without problem, with new configuration (see later) I have this
problem:
An error occurred loading a configuration file: Failed to start monitoring
changes to [...] because the network BIOS command limit has been reached. For
more information on this error, please refer [...]
So, I've found in other newsgroup a possible cause that is authorization on
my local ASPNET user... In short, my ASPNET user couldn't to "observe" file
changes over the share folder...
This is my network architecture:
[dev client (my notebook)]
WinXP Prof SP2
Logon user is a local user; I've 3 map network drives on the dev server (c$,
d$ and webSite folder)
However I've configured my web project to access to absolute path
(\\myServer\myShare and not to O:\myShare)
[dev server]
Win2003 + IIS6
2 disks
C
|-Program Files
|-Windows
|-Microsoft.NET
|-Framework
|-v2.0.50727
|-Temporary ASP.NET Files
D
|-InetPub
|-wwwroot
|- myShare (<-- pratically every user has permission to this
share, and is authorized from Security Tab)
When I try to build my web site from my VS2005 (Team Edition from Software
Developer version 8.0.50727.42) I get previous error... Can I solve the
problem? Must I change configuration of my solution?
Thanks
--
Omar
Steven Cheng[MSFT] - 02 Feb 2006 06:51 GMT
Hi Omar,
Regarding on the remoted shared website build/compiling problem in VS 2005,
from the error message and the description, it is also possibly caused by
the network share's setting (NT Lan Man ) between the server and client
machine. As far as I know, when opening website from remote fileshare, the
VS IDE will do lots of file manipulation operations to server share through
the LM SMB protocol, and there is one connection limitation which can cause
this problem. Here is the kb article mentioned this:
#"The network BIOS command limit has been reached" error message in Windows
Server 2003, in Windows XP, and in Windows 2000 Server
http://support.microsoft.com/kb/810886/
Also, you can try testing from a win2k3 server machine (as the client)
which have VS 2005 installed and open the remote share through file system
to see whether it works.
Thanks,
Steven Cheng
Microsoft Online Support

Signature
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)