Opportunistic locking help

[Duncan]

Dear All, Hope you can help...

In a previous post, Brian suggested disabling op locking:

You could always disable op locking to see if the behavior
changes. I would
share the files from a server, it handles it better. Check
out this article.

296264 Configuring Opportunistic Locking in Windows
http://support.microsoft.com/?id=296264
--

Best regards,
Brian Oakes, MCSE

So I checked the opportunistic locking doc and found that
the parameters folder does not contain any such entries -
only 'Cscenabled'

Should I create all the Registry entries or is there a
reason why they are not there?

I have also checked the client machines when I have file
access problems and when the Client machine waits for
several minutes trying to open
the file, system monitor reports 100% cpu usage.

Any help would be greatly appreciated!


Kind Regards Duncan

 

[Brian Oakes [MSFT]]

If a registry value isn't listed then it is set to the deafult setting. ie
if the article says that it is enabled by default and the value is set to 1
in the article, then you assume it is set in the registry as such.

Set as follows as a test

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\

OplocksDisabled REG_DWORD 0 or 1
Default: 0 (not disabled)

Set to 1

NOTE: The OplocksDisabled registry value configures Windows clients to
either request or not request opportunistic locks on a remote file.

You can also deny the granting of
opportunistic locks by setting the following registry entry to 0:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

EnableOplocks REG_DWORD 0 or 1
Default: 1 (Enabled by Default)

Set to 0

--

Best regards,
Brian Oakes, MCSE
Microsoft Product Support
Windows 2000 Server Networking Team

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.

 

[Duncan]

Dear Brian,

Thanks for the info, I tried this but it made no
difference.
Something else I spotted:

I tried to open a word document located on the server from
a win98 machine and got a long pause while it tried to
open it & then an error message from word saying it didn't
exist... When I checked the open files on the 2000
machine, it reported that I had an exe file opened -
definately not the case! You can usualy tell when the
win98 client will not open the word doc as the file does
not highlight during the first mouse click of the double
click if you see what I mean.


Kind Regards Duncan

 

[Marina Roos]

Duncan,

I thought you had a W2K acting as a server, but it's not W2K-server, is it?
Anyway, make sure you've installed the ms03-026 patch on all W2K-boxes.

Marina

 

[Marina Roos]

That's what I meant. W2K Pro is the workstation version, W2K Server is the
serverversion.

Marina