Locking Bug in Client for Vista 2

allendorfer <allendorfer@no-mx.forums.novell.com> wrote:

> Client for Vista v1 and v2 have a locking bug:
> ...
> Client32 doesn't have this problem

LAN trace confirms that the byte range actually does have an unlock
request occurring on the wire from the first station, and the server
returns a successful response to the unlock request. But the second
station attempts to lock that same byte range, and receives a lock
failure anyway.

The difference between Novell Client for Windows Vista/2008 and Novell
Client for Windows XP/2003 shown in the LAN trace is that Vista/2008
is using NCP 87,68 ("release the lock I'm holding on this byte range,
but leave the byte range recorded in my log table in case I want to
re-lock it later as part of a set / NCP 110"). Versus XP/2003 which
is using NCP 87,69 ("release the lock I'm holding on this byte range,
and remove it from the log table entirely because I don't intend to
re-use that range").

This issue did not replicate for me on OES 2 SP2 Beta 4.4 on SLES 10
SP3 Beta 1.1 for what its worth; NetWare appeared to be the only
affected platform.

So on the surface it would appear that the NCP server / NSS is not
honoring the "release lock on this byte range" properly, not
withstanding that Vista/2008 is using a different unlock NCP than
XP/2003 employs. Registered as Bug 529054 against NetWare 6.5, should
you ever need to open a support call or otherwise refer to it.

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)