Hi, All. Here's what happened today: Joanne opens an Excel spreadsheet on the Samba share "public", but for some reason Excel crashes. Some twenty minutes later, Anna attempts to open the same spreadsheet and receives the warning that Anna already has opened the file. (That's right, Anna, not Joanne.) When I run smbstatus, the lock shows up as belonging to Joanne, which is how I know who to call and ask her to log out and in again. I also killed Joanne's connection via Swat. Anna then receives notification that the file is available for editing. So here are my questions: 1) Why did Anna receive the lock notice that Anna already had the file open? I can understand that the lock was left, but shouldn't the locking user have been properly identified? 2) Is there some way to convince Samba to release a lock if the client application has crashed? Or will this be an ongoing admin problem? We're running Samba 2.0.7 under VA Linux Red Hat 6.2, kernel 2.2.14-5.0.14smp. Thanks in advance for any suggestions. -Bill