Archives that remain opened after use

[Jorge Moreno]

Hello, coleagues.
I have a TC4100 and some pc's working against archives stored in this machine. When some of this pc's open a word or excel archive of the server and close this after work, the archive remains opened, sometimes along days. Of course when the user tries to open again the archive he can't.
Does anybody knows what's happening.
Thanks.

[chuck berry_3]

This article may apply:

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B112825&Product=WRD

UNC Connections Don't Disconnect Immediately

UNC Connections Don't Disconnect Immediately
View products that this article applies to.
This article was previously published under Q112825
SYMPTOMS
When 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.EXE

and 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.
CAUSE
The cause of this problem is currently under investigation.
WORKAROUND
Shorten 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
\Parameters

Add 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.
STATUS
Microsoft 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.