Followup on: File lock reporting problem & NWScanPhysicalLocksByFile

On Sun, 11 Jun 2006 08:33:24 GMT, "Wolfgang
Schreiber"
<nojunkjunk.com> wrote:

>Just a guess: Could it be a matter of different service
pack levels or 
>different priviledges on the two servers?
>
>Wolfgang
>
>"Loren Pechtel" <lorenpechtelhotmail.invalid.com> wrote in message 
>news:fWDig.8176$8_3.7953prv-forum2.provo.novell.com...
>> On Sun, 04 Jun 2006 01:06:53 GMT, Loren Pechtel
>> <lorenpechtelhotmail.invalid.com>
wrote:
>>
>> I really don't understand it now--it's the
server, not the
>> workstation.  On another Netware 6 server it works
fine. 

Both are patched to SP5.  It's possible the other one has
some patches
this one doesn't have.  Any ideas of anything relevant?

It's not privledge levels--in both cases it's accounts
with full
access and besides the same errant non-reporting of locks
can be
observed through monitor on the server itself.

(Speaking of privledge levels, there's a bug.  Why can I
find out who
has the file open with normal access but I need admin
authority to
find out who has locks on it???  And what's with the
privledge needed
being "console operator"--something that
doesn't seem to appear
anywhere else?)