KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q153070: Some IPC$ Connections Cannot Be Disconnected

Article: Q153070
Product(s): Microsoft Windows NT
Version(s): 3.5,3.51
Operating System(s): 
Keyword(s): 
Last Modified: 22-FEB-2002

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows NT Server versions 3.5, 3.51 
-------------------------------------------------------------------------------

SYMPTOMS
========

When you connect to a Microsoft Windows NT version 3.51 server share, an initial
connection is made to IPC$ and the connection is assigned to the username in
Server Manager. This connection should drop off after the username has been
authenticated, but it does not. However, it can be disconnected manually in
Server Manager as long as the connection is still associated with the username.

Once you disconnect from the resource, the IPC$ connection is enabled until
Autodisconnect disconnects it. At the point that you disconnect from the
resource, the IPC$ connection is associated with your computer name. The IPC$
connection cannot be broken in Server Manager. Autodisconnect will break it
unless it has been made unavailable.

RESOLUTION
==========

1. Enable Autodisconnect and set for a time appropriate for your environment.
  This can be done via the command line:

  NET CONFIG SERVER /AUTODISCONNECT:<minutes>

  NOTE: The Windows NT Server service is self-tuning, normally the server
  configuration parameters are auto-configured (calculated and set) each time
  you boot Windows NT. 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 changed any of the Server
  service settings, Windows NT is no longer able to automatically tune the
  Server service for your new configuration. To avoid losing the Server
  service's auto self-tuning capability, make the change through registry
  editor instead from a command line or Control Panel Network.

  For more information, see the following articles in the Microsoft Knowledge
  base:

  Q128167 Server Service Configuration and Tuning

  Q138365 How the Autodisconnect Works in Windows NT

2. Make an explicit connection to the IPC$ share and then disconnect from it.

  NET USE \\servername\ipc$
  NET USE \\servername\ipc$ /d

  -or-

3. Upgrade to Microsoft Windows NT version 4.0, where this problem has been
  corrected.

Additional query words:

======================================================================
Keywords          :  
Technology        : kbWinNTsearch kbWinNT351search kbWinNT350search kbWinNTSsearch kbWinNTS351 kbWinNTS350 kbWinNTS351search kbWinNTS350search
Version           : :3.5,3.51

=============================================================================

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.