Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...the infamous Network BIOS Command limit has been reached error the infamous Network BIOS Command limit has been reached error
Previous
 
Next
New Post
2/11/2009 5:40 PM
 

 

Hi

I am attempting to setup a hardware loadbalanced webfarm for dnn.  I am running 2 frontend VMWARE servers on win2k3 and running sql2008 on the backend. I have followed every lead possible on this error and still am not getting anywhere. 

An error occurred loading a configuration file: Failed to start monitoring changes to '\\myserver\dnn\admin\moduledefinitions' 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. (\\myserver\dnn\admin\moduledefinitions\web.config)

I am testing on just one web server at the moment, and testing with a unc fileshare on a test server (will be going on our EMC san once i figure out how to get it working)   DNN installed fine after performaning a few caspol commands, and setting the app pool to run as a domain user .  I am able to browse the site perfectly fine, after a fresh iis reset, however after about a minute or 2 i get the network bios error.  I had followed shannons directions for a fix with no luck.

1. Create a user who will run the .netnuke app pool and who has modify access to the unc path
 1.1 Modify security permissions so the user can run the app pool.
 1.1a C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -ga <user>
 1.1b gpedit.msc  (Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignments)
  Grant "Adjust memory quotas for a process", "Logon as a service" and "Replace a process level token"
2. Create the app pool and set the identity
3. Create the website with the home directory as the remote share and app pool as created above
4. regedit HKLM\Software\Microsoft\ASP.NET create DWORD "FCNMode" value 2  (This was part of a hot fix but what the document doesn’t say is it also applies to .net sp1 and above)

5. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -q -m -ag 1 -url "file:////\\<server>\<share>\*" FullTrust -exclusive on
6. iisreset

as well as following http://support.microsoft.com/kb/810886

Searching google and the forums keeps turning up that article and it doesn't help at all.  Does anyone have any suggestions or experience with the same situation ?  any help would be GREATLy appreciated

 
New Post
2/11/2009 7:50 PM
 

There was a similar thread posted this week, suggest you search for this and possibily tail on the top of it.



Alex Shirley


 
New Post
2/11/2009 9:50 PM
 

 Hey Ryan,

Please give me a call.  I'm sure we can help you out.

My number is 402-650-6072.

 

 

 
New Post
2/11/2009 10:36 PM
 

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/285914/scope/posts/Default.aspx (paul has updated the post as well, hope this works...)



Alex Shirley


 
New Post
2/12/2009 8:07 AM
 

I tried pauls suggestion as well, (forgot to mention that in my original post) 

The problem with the lanmanworkstation and lanmanserver registry keys is that if the lanmanserver keys need to be edited on the server with the fileshare, that can only be done in my situation when setting up a windows unc share.  when i move this to the enterprise nas, i will not be able to set that setting on the server as it is an EMC unit, which is for the most part unix based , and will not have that registry key.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...the infamous Network BIOS Command limit has been reached error the infamous Network BIOS Command limit has been reached error


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out