We are deploying Framework 2.0 and DotNetNuke 4.6.2 to our web farm for the first time, and it brought down the farm!

Out farm involves 5 servers:

S1   Windows 2003 Server
S2   Windows 2000 Server
S3   Windows 2000 Server

SNAP file server
Database server - SQL Server 2000

We set up a share on the SNAP server, and put our source there.  The source files all worked fine when run locally.
WIthin IIS on each, we we configured the Home Directory to "A share located on another computer", and pointed the Network directory to the share on the SNAP server.

The error:  "Error 1 An error occurred loading a configuration file: Failed to start monitoring changes to \\IpAddress\shareName because the network BIOS command limit has been reached.  Please refer to KB 810866.  Hosting on a UNC share is not supported..."

Has anyone seen this?  Does the fact that the share is UNC instead of mapped drive play in?  We've tried KN 810866, but if there's a magic combination, so far we haven't hit it.

TIA,

Don Stuber

Your "Plog" was very helpful, Penny.  Thanks!   I have solved several permissions issues.  Unfortunately, I still get "network BIOS command limit has been reached".  I have raised MaxCmds and MaxMpxCt to 4096 on both the file server and  the IIS server.  4096 helped some, but only delayed the inevitable:  within a handful of page accesses, DNN again reported the error.

While we need to go live with DNN in the web farm, I'm only working in a test environment for now until we solve this one.  The test environment has but one web server, one file server, and one SQL Server, all on different OS installations.  Of the 3, two are on virtual machines, and two physical machines are involved.

What would you recommend trying next? 

Don Stuber

Bump