User Limits vs. Hanging Client Connections
Posted on 2006-06-01
Here's the deal... it seems as though placing user limits on a particular shared resource doesn't work the way it should. I'm running Server 2003 as a file server only. The problem we've had is that when 8 supervisors are trying to update a task list in Excel by updating the same .xls file, all on the same morning before our weekly meeting, someone opens it and makes changes, but before they save their copy, someone else opens that same file, therefore overwriting the first person's changes when they click 'Save'.
My solution: Compartment the spreadsheet in its own folder and set that folder's USER LIMIT to "1". Sounds great, right? If someone gets the error 'Resource cannot accept additional users', they'll know that someone else is already in that folder and will have to wait their turn, but at least no one will overwrite someone else's changes...
Problem is, when user #1 closes the spreadsheet and closes out the folder (the entire window), Server 2003 still shows that shared folder as having 1 Client Connection, even though that user is not listed in the 'Sessions' list in Computer Management. The connection isn't terminated until user #1 logs off the client machine. When 7 more supervisors need to update their portion of that spreadsheet in the same morning, having a User Limit doesn't seem to do what its supposed to...
How can we force Server 2003 to terminate inactive client connections once (preferably, as soon as) the client has closed that window and is no longer viewing the folder or its data?