Opportunistic Locking...?

  • Thread starter Thread starter Kenneth
  • Start date Start date
K

Kenneth

Howdy,

We run Paradox as our database on a peer-to-peer Win 2000
Lan.

I researched an error we were getting on occasion and
learned that we needed to turn off opportunistic locking in
the registry.

The location was:

HKLM\System\CurrentControlSet\Services\MRXSmb\Parameters

and we were to be sure that on all systems there was an
entry for EnableOplocks with a value of "0".

We checked our machines and made the setting where
necessary.

All was well until the last machine:

On that system, Services does not appear at all under
HKLM\System\CurrentControlSet.

On that machine, we searched for "EnableOplocks" and found
it at:

HKLM\System\ControlSet002\Services\LanmanServer\Parameters
where it appeared, correctly set to "0".

Might you help me to understand what all this is telling me?

Very sincere thanks for any information on this,
 
In said:
Howdy,

We run Paradox as our database on a peer-to-peer Win 2000
Lan.
Click to expand...

Is that a DOS version of Paradox? The solutions may be different
in that case, but it has been many years since I last dealt with
that.
I researched an error we were getting on occasion and
learned that we needed to turn off opportunistic locking in
the registry.

The location was:

HKLM\System\CurrentControlSet\Services\MRXSmb\Parameters
Click to expand...

You may find that the "solution" differs between Server settings
and Client settings. Try these two Tips at
jsiinc.com 1447 9316
for a little background. I pretend no expertise in this area
however.
and we were to be sure that on all systems there was an
entry for EnableOplocks with a value of "0".

We checked our machines and made the setting where
necessary.

All was well until the last machine:

On that system, Services does not appear at all under
HKLM\System\CurrentControlSet.
Click to expand...

That could be indicative of malware (present or past) and suggest
full scans with multiple tools. Also RootkitRevealer (free
Sysinternals) may reveal some anomalies (not necessarily a rootkit)
that would be clues to this. Also Try a "Safe Boot" perhaps.
On that machine, we searched for "EnableOplocks" and found
it at:

HKLM\System\ControlSet002\Services\LanmanServer\Parameters
where it appeared, correctly set to "0".

Might you help me to understand what all this is telling me?
Click to expand...

Only that the LanManServer and the MXRSMB are not equivalent and
(aside from the missing CCS\Services) that if "2" was listed as
"Current" at HKEY_LOCAL_MACHINE\SYSTEM\Select
you at least have the correct control set.

Not sure if any of this will be helpful.
 
Back
Top