What about this? The hotfix is linked in the article. http://support.microsoft.com/default.aspx?scid=kb;en-us;272582 Windows 2000 Terminal Services Incorrectly Closes Files on Remote Shares The information in this article applies to: Microsoft Windows 2000 Server SP1 Microsoft Windows 2000 Server SP2 Microsoft Windows 2000 Advanced Server SP1 Microsoft Windows 2000 Advanced Server SP2 This article was previously published under Q272582 SYMPTOMS You may receive one or more of the following error messages when multiple users on a Terminal Server work with the same files that are located on a network share: Disk or Network Error STATUS_UNEXPECTED_NETWORK_ERROR (0xc00000c4) ERROR_UNEXP_NET_ERR (error 59 in decimal or 0x3b in hexadecimal) STATUS_CONNECTION_DISCONNECTED (0xc000020c) ERROR_NETNAME_DELETED (error 64 in decimal or 0x40 in hexadecimal) CAUSE This problem can be caused when the user that first opened the shared file logs off. The Terminal Server incorrectly closes the file handles that it has open to the remote file, so any other programs that had the file open are no longer able to access the file. Note that this problem does not occur if the data files are moved to a local volume on the Terminal Server. RESOLUTION To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 260910 How to Obtain the Latest Windows 2000 Service Pack The following file is available for download from the Microsoft Download Center: Q272582_W2K_SP3_X86_EN.exe The Q272582_W2K_SP3_X86_EN.exe file contains the following files: Mrxsmb.sys Rdbss.sys For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: 119591 How to Obtain Microsoft Support Files from Online Services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on secure servers that prevent any unauthorized changes to the file. NOTE: This hotfix addresses scenarios where data files reside on network shares. Executable images must run from a local partition. WORKAROUND To work around this problem, move the data files to a local volume on the Terminal Server. If hard-coded drive letters are required by your program, you can use the SUBST command to map these drive letters to a local volume. STATUS Microsoft has confirmed that this is a problem in Windows 2000. This problem was first corrected in Windows 2000 Service Pack 3. MORE INFORMATION The best way to identify this problem is to look at a trace. In the trace you can see that the Terminal Server initially sends an SMB Close for the file handle of the file that is being used by user A. This happens when the user quits the program. When user A then logs off, the Terminal Server sends an SMB Close for any other file handles that are outstanding on this file that was in use by user A, even if those file handles were not obtained by user A. For example, you might see the following behavior in the trace if multiple users were working with a Microsoft Access database file: User A quits Access. SMB Close for the file handle for the database file. User A logs off. SMB close for the file handle that user B obtained to open the database file. -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Beckman Sent: Monday, January 13, 2003 4:26 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] TS file locks has anybody heard of this? and if so what is the work around? We are seeing this happen. Does anyone else run a .exe on the citrix server and the working dir. on a file srever? When a Terminal Services <javascript:winPop('http://www.winnetmag.com/FindIT/Index.cfm?ID=55')> client connects to a network device, the Windows network redirector component creates a file control block (FCB) that handles the state of open files. When multiple users running Terminal Services sessions connect to the same network resource, a bug in Win2K prevents the network redirector from creating more than one FCB. As a result, when one user disconnects, the OS closes the FCB, which terminates all other remaining user connections. If the remaining users were accessing data on the network resource, they will receive the following error message: Disk or Network Error If the remaining users were running a program on the network resource, the application might exit or display the following error message: C0000006 : In Page I/O Error Microsoft currently has no fix for this problem, although the same error doesn't exist in Windows .NET <javascript:winPop('http://www.winnetmag.com/FindIT/Index.cfm?ID=1')> Server (Win.NET Server). Microsoft recommends that Win2K users copy all network resources to the local machine, then then use the Subst command to create a dummy drive letter that points to the local path. However, the whole point of creating network resources is to be able to share those resources, and I doubt most users will follow Microsoft's recommendation. *********************************************** This Weeks Sponsor: WM Software WMS Messenger for TSE Affordable Instant Messaging for Terminal Servers http://www.wmsoftware.com/wmsm/ ************************************************ For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm *********************************************** This Weeks Sponsor: WM Software WMS Messenger for TSE Affordable Instant Messaging for Terminal Servers http://www.wmsoftware.com/wmsm/ ************************************************ For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm