I'm experiencing a problem which I have tried to resolve
for a long time now, we are running 18 clients on
WindowsXP Pro and they are connected to a Win2k server.
Files which are stored on the server are accessed by
various users to input various information and then saved
and closed. After several sessions the file becomes
locked and when the user opens the file again the user is
warned that another user is using the file. When the user
then tries to save the file the system generates an error
that the file cannot be saved and that a temporary file
has automatically been created (I have confirmed that in
these instances the file being accessed was not being used
by anyone else).

I have run through the knowledgebase and have found
various articles dealing with "lanmanserver" registry keys
specifically the EnableOplocks and OplocksDisabled keys,
it has made an improvement on the network but the users
still occasionally experience the same problem and when I
check the openfiles on Computer Management the files which
users reported having problems editing either have "4","3"
or "2" locks on it. What is still causing this problem and
how can I resolve it? This problem is not consistent as
it doesn't happen all the time only sometimes but I can't
see the cause of the problem and don't know if it is a
Win2k server issue or a WinXP Pro issue.

Hi Miguel,

It's mainly an XP-thing.
Have a look at articles 329170, 810907, 812937, 811492, 321169 and 296264.

Marina

"Miguel Serra" <(E-Mail Removed)> schreef in bericht
news:05ee01c3b278$41e3e5a0$(E-Mail Removed)...
> I'm experiencing a problem which I have tried to resolve
> for a long time now, we are running 18 clients on
> WindowsXP Pro and they are connected to a Win2k server.
> Files which are stored on the server are accessed by
> various users to input various information and then saved
> and closed. After several sessions the file becomes
> locked and when the user opens the file again the user is
> warned that another user is using the file. When the user
> then tries to save the file the system generates an error
> that the file cannot be saved and that a temporary file
> has automatically been created (I have confirmed that in
> these instances the file being accessed was not being used
> by anyone else).
>
> I have run through the knowledgebase and have found
> various articles dealing with "lanmanserver" registry keys
> specifically the EnableOplocks and OplocksDisabled keys,
> it has made an improvement on the network but the users
> still occasionally experience the same problem and when I
> check the openfiles on Computer Management the files which
> users reported having problems editing either have "4","3"
> or "2" locks on it. What is still causing this problem and
> how can I resolve it? This problem is not consistent as
> it doesn't happen all the time only sometimes but I can't
> see the cause of the problem and don't know if it is a
> Win2k server issue or a WinXP Pro issue.