Cannot Access Files on Novell 3.11 ServerLast reviewed: April 9, 1996Article ID: Q130710 |
The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, you should first make a backup copy of the registry files (System.dat and User.dat). Both are hidden files in the Windows folder.
SYMPTOMSWhen you try to access a file on a NetWare 3.11 server from a Windows 95- based computer using the Microsoft Client for NetWare Networks, you may receive one of the following error messages:
When you send a message from Microsoft Exchange, if the post office is located on a Novell 3.11 server, you may receive the following error message:
The message recipients mailbag does not exist or is busy. Contact your administrator. CAUSEThese errors occur when a File Open request is sent to a NetWare 3.11 server but the client does not properly receive a "file open success" message. This causes the File Open request to be repeated. Under normal circumstances, the server would resend the "file open success" message to the client. However, the server returns a "file already open" failure message to the client instead. This error occurs only when you are opening a file on a NetWare 3.11 server with the OS/2 namespace module loaded on the server and long file name support enabled on the client. Therefore, the error does not occur when you are using a Novell work-station shell (NETX or VLM). Note that this error does not occur on NetWare version 3.12 or higher servers.
RESOLUTIONOnce the file has been left open on the server, it must be closed to resolve the error. To prevent the error from occurring, use one of the following methods:
MORE INFORMATIONTo disable long filename support on the Microsoft Client for NetWare Networks, use either of the following methods:
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows 95. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
|
KBCategory: kb3rdparty kbnetwork kbenv kberrmsg
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |