Server Service Configuration and Tuning

Last reviewed: September 4, 1996
Article ID: Q128167
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SUMMARY

Although the Windows NT Server service is self-tuning, it can be also be configured manually through Control Panel Service. Normally, the server configuration parameters are auto-configured (calculated and set) each time you boot Windows NT. However, if you run NET CONFIG SERVER in conjunction with the /AUTODISCONNECT, /SERVCOMMENT OR /HIDDEN switches the current values for the automatically tuned parameters are displayed and written to the registry. Once these parameters are written to the registry, you cannot tune the Server service using Control Panel Networks.

If you add or remove system memory, or change the server size setting minimize/balance/maximize), Windows NT does not automatically tune the Server service for your new configuration. For example, if you run NET CONFIG SRV /SRVCOMMENT, and then add more memory to the computer, Windows NT does not increase the calculated value of autotuned entries.

Typing NET CONFIG SERVER at the cmd prompt without additional parameters leaves auto tuning intact while displaying useful configuration information about the server.

MORE INFORMATION

The Server service supports information levels that let you set each parameter individually. For example, the command NET CONFIG SRV /HIDDEN uses information level 1016 to set just the hidden parameter. However, NET.EXE queries and sets information levels 102 (hidden, comment, users, and disc parameters) and 502. As a result, all parameters in the information level get permanently set in the Registry. SRVMGR.EXE and the Control Panel Server query and set only level 102 (not level 502) when you change the server comment.

Administrators wishing to hide NT computers from the browse list or change the autodisconnect value should make those specific changes using REGEDT32.EXE instead of the command line equivalents discussed above. The server comment can be edited using the description field of the Control Panel Server applet or Server Manager.

RESOLUTION

To restore the LAN Manager Server parameters to the defaults, or to reconfigure Windows NT so that it auto-configures the Server service:

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

  1. Run Registry Editor (REGEDT32.EXE).

  2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

          \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
    

  3. Remove all entries except the following:

          EnableSharedNetDrives
          Lmannounce
          NullSessionPipes
          NullSessionShares
          Size
    

    NOTE: You may have other entries here that are statically coded. Do not remove these entries.

  4. Quit Registry Editor and restart Windows NT.


KBCategory: kbnetwork
KBSubcategory: ntnetserv
Additional reference words: prodnt 3.10 3.50 auto configure tune tuned
tuning



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 4, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.