I work for a major mortgage company in the US where we have several developers who use dnn.  As a systems admin for the web tier,  I get to deal with it when the apps crash or need a hand. 

Unfortunately, we have been seeing NetBIOS connections get eaten up consistently, thus bringing down the application.  We have no idea why this is happening, as the applications themselves are extremely small.  I have seen this occur in a shared hosting environment as well, but right now my concern is the enterprise level environment. 

Does anyone have any information on a setting we can change or a tweak we can make in order to correct this.  From everything I have found, this is a known issue, but has no real correction for it.  If this is true, it may not be ready to run in the environment we have, which would be a shame because of how much the developers like the ease of deployments with DNN.  Any assistance anyone can offer would be greatly appreciated.

Please provide more info on the configuration of the server and what other functions it is used for.  DNN, as the Web based application it is, does not use NetBios at all.  From the description in your post I think you are getting things mixed up.  You may be having a real problem with NetBios but that has nothing to do with DNN.  DNN only uses the HTTP protocol on port 80.

FYI, if all the client computers on your network are Windows 2000 and above, and so is the server, you can remove the true NetBios protocol as you can have the NetBios functionality over TCP/IP.  I would seriously explore this option.  The pure NetBios protocol is obsolete and rarely needed.

Carlos

In my opinion it must be something else, NetBios is not even a protocol option for SQL Server, therefore a DNN module, as misbehaved as it may be, will not use it.  I would not recommend messing with the DNN installation.  Look at other things being used on the server.

Are there a lot of files shared from the server?  Or MS-DOS style applications that connect to it?

Smith, we cannot help you without more details about your configuration.  Again, tell us the specific error message you are getting, the configuration of the server, and a description of the network in general including the kind of clients that connect to the server (do you have any Windows 95/98 clients for instance).

Carlos