Microsoft KB Archive/142625

= NETBIOS Defaults To 16 Sessions on Windows NT =

Article ID: 142625

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition

-



This article was previously published under Q142625





SYMPTOMS
On your computer running Windows NT, after your NETDDE application connects to 16 nodes a NetDDE error is reported periodically to the event log and a 17th connection to another node is prohibited.

In Windows NT, the default maximum number of sessions (connections) that a NetDDE application program can request is 16. For NetDDE applications, each NetBIOS session is a connection to another node. Therefore, the maximum number of nodes that a DDE server can connect with NetBIOS is currently limited to 16 nodes.



CAUSE
In the NetDDE NetBIOS dynamic link library (NDDENB32.DLL), the NetBIOS reset command is currently set to the default value of 16 for the maximum number of sessions.



RESOLUTION
Install the fix referenced below (under STATUS) and modify the registry as follows:

WARNING: Using Registry Editor can cause serious, system-wide errors that may require you to reinstall Windows NT. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

 Run the Registry Editor(REGEDT32.EXE). Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:

 If the value is not defined in the right window pane, choose Add Value from the Edit menu.  Type or select the following information when prompted with the field names on the left:

   Value Name: MaxSessions Date Type  : REG_DWORD Data             :

where is a value from 0 to 254. If it is set to zero, it defaults to 16 sessions maximum. 

NOTE: If the value is not defined in the registry, it defaults to 16 maximum sessions.

<div class="status_section">

STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51 and 4.0. This problem was corrected in the latest Windows NT U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: prodnt

Keywords: kbnetwork KB142625

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.