Error Code 8804

  • 10021929
  • 1.0.39892527.2410901
  • 18-Nov-1999
  • 30-Jun-2003

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Fact

Novell NetWare 4.11

Novell NetWare 5.0

Novell Client 4.6 SP2 for Windows NT

Formerly KB 2927977

Symptom

Error Code 8804

Error: "LOGIN-4.21.15-430: The following drive mapping operation could not be completed.  [F:=<SERVER>\SYS:] The error code was 8804."

Error: "LOGIN-4.21.15-430: The following drive mapping operation could not be completed.  [INS S1:=<SERVER>\SYS:PUBLIC]" The error code was 8804."

Error: "LOGIN-4.21.15-430: The following drive mapping operation could not be completed.  [ROOT J:=.<Organization>_SYS.<SERVER>:\<DIRECTORY>\<DIRECTORY>] The error code was 8804."

Erratic results during login as to how server specific information is displayed.

Cannot run DSREPAIR to check volume objects and trustees.

Error "Trustees can not be checked" which brings up the DSREPAIR.LOG file.

Unable to map a drive to the server.

Double-clicking on the server in explorer brings up tree information when it should be bringing up volume information.

Double-clicking on the Tree in explorer brings up volume info when it should be bringing up tree information.

Problem does not seem to appear with the Novell Client for Windows 95/98.

Cause

The Tree, Server, and Organization Unit are the same name.  The Server name and the Tree name both SAP out in DS and have to be unique because of this fact. The requests issued from the client could be interpreted either by the server or the tree and erratic results will occur.

The reason is because the client name/address resolution process does not know what is being requested (trees or servers)-- all it knows is a name or an address--there is no context information with it. Among the widely varying LAN/WAN configurations, protocol selections, and client configurable parameters related to name resolution, it is nearly impossible for the client to always get it right when in mixed environments e.g. SAP/Bindery and NDS.

A packet trace shows that the client requests the tree info and then uses the tree entry ID to request the path attribute to the server.

Fix

Tree and Server names must be unique.  It is recommended the container holding the server have a different name as well, but is not a requirement.