WFW 3.11 Clients Hang Accessing Windows NT ServerLast reviewed: September 25, 1996Article ID: Q123029 |
The information in this article applies to:
SYMPTOMSWindows for Workgroups version 3.11 hangs when you run a database application that is using a shared file on a Windows NT server.
CAUSEThis problem involves oplock, byte-range lock, and lock-&-close server message block (SMB) protocols. The behavior that causes this problem is as follows:
A deadlock condition occurs since CLIENT1 thinks that the file handle was closed and therefore will never unlock the byte range.
RESOLUTIONA workaround for this problem is to turning off opportunistic locking at the file server.
STATUSMicrosoft has confirmed this to be a problem in Windows 3.11. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.
|
KBCategory: kbnetwork kbinterop
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |