UNC Connections Don't Disconnect ImmediatelyLast reviewed: April 11, 1997Article ID: Q112825 |
The information in this article applies to:
SYMPTOMSWhen running a program over a UNC connection, the connection remains open until it is released by means of the AutoDisconnect or KeepConn timeout value. For instance, if you run WINWORD over the network using the command line
\\Server\WINWORD\WINWORD.EXEand then close WINWORD, its files remain open until either the workstation or the server explicitly disconnects. This happens with any application run over a UNC connection.
CAUSEThe cause of this problem is currently under investigation.
WORKAROUNDShorten this time-out value on the workstation by changing the KeepConn value to a lower value. If you are using Windows NT, you can change this value in the Registry. WARNING: Using the 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 the Registry Editor can be solved. Use this tool at your own risk.Under this Registry path:
HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet \Services \LanmanWorkstation \ParametersAdd the value 1 to KeepConn to make it drop the connection after one second of inactivity. This drops only implicit connections such as those created when you use a UNC connection; it does not drop your drive connections.
STATUSMicrosoft has confirmed this to be a problem in Windows NT and Windows NT Advanced Server version 3.1. We are researching this problem and will post new information in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: prodnt
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |