Ed,

Thanks very much for the additional info. The sporadic "file left in use" is so rare, I don't think I want to impose on you to search for the registry hack.

My original problem, with widespread file problems and even renaming of shared folders to things like "delta-c", is still a bit of a mystery. A second network guy looked at the client's system and said he found they were running a "developers edition" of NT4 with built in user limits. Not sure how this happened.

Anyway, they are upgrading to NT2000 and we are limping to that point.

Thanks,

Larry


>
>It's actually not a hiccough; it's a known behavior of NT Server for files that have been 'disconnected' from but their session has been left open (there's an active session for the share that has neither explicitly been released nor has reached the inactivity timeout limit, which can be quite large with some versions of NT 4.0 if nothing has been done to alter the defaults. There's a registry hack to force NT not to cache connections until termination of a session; it can be found in the MSKB; I can look it up if necessary (I have the Win2K equivalent on hand, but have done in all my NT Servers, so the registry key hack has been moved to archival storage (aka the stack of papers on the far rear left of the desk...)
>
>>It seems different than this wholesale foul up that seems to include renaming of shared folders. If (when?) I get a solution, I'll post it here.
>>
>
>You'd be best served by releasing the share, renaming the file, and only then recreating the share.