General discussion
March 20, 2002 at 03:26 AM
shanghai sam

NT4 delays release of shared resource

by shanghai sam . Updated 24 years, 5 months ago

On an NT4.0 server (SP6a), I have a shared folder to which I only allow access to 1 user at a time.

I use a batch file that starts with a “net use” command to map the folder to a drive letter. It then launches the program in that folder. When the user closes the program, the batch file ends with another net use command and the /d switch to disconnect the mapping and make it available for another user.

When I first used this on an NT4.0 workstation, the Server did not immediately free upthe shared resource after the batch file finished. Under Server Manager | Properties for (the server) | Shares, I still showed as a Connected User. Although the “In Use” column showed “No” the “Uses” column for the “Sharename” above showed “1”.I solved the problem by using the net use command…/d twice at the end of the batch file: first using the mapped drive letter and then using the UNC path. This caused the shared resource to free up immediately on the server.

However, I’m back to the same problem now with an XP Pro client machine. It takes 1 minute to release on the server. The fix that worked for NT4 does not work for XP.

Any ideas?

This discussion is locked

All Comments