Drive mappings fail when logging in

  • 7015753
  • 08-Oct-2014
  • 08-Oct-2014

Environment

Novell Client 2 SP3 for Windows
OES

Situation

Intermittently when users login, drive mappings to certain servers fail.  

Errors may include:

LOGIN-LGNWNT32-430: The following drive mapping operation could not be completed.
[F:=.SERVER1_SYS.SERVERS.COMPANY:\]
The error code was c000014f.
LOGIN-LGNWNT32-430: The following drive mapping operation could not be completed.
[G:=.SERVER1_VOL1.SERVERS.COMPANY:\]
The error code was c00000be.
 
When browsing the available network resources in Explorer, there may be multiple entries for the server name. When clicking on the invalid entry, an error such as the following may appear:

Open Folder
\\SERVER1 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The network address is invalid.

Resolution

Locate the device which is advertising the duplicate name and correct the configuration.

Cause

Another service, such as CIFS or Samba, may be advertising the same name as the NCP server.

Advertised names should be unique. The CIFS service running on a Novell NCP server is usually named with "_W" appended to the name. For example: SERVER1_W.

Additional Information

Use a LAN trace (Wireshark or similar) to view the network traffic when attempting to access the invalid resource.

In the trace, search for the name of the device. You may see an request such as:

Protocol: LANMAN
NetServerEnum2 Request, Workstation, Server, Domain Controller, Time Source, Apple server, Novell...

And the response such as:

Protocol: LANMAN
NetServerEnum2 Response

which would include an entry for the server name in question.

Samba

To verify that this is problem with Samba, first see if Samba is running on the server by typing this command at the server console:

rcsmb status

If it is running, stop the Samba service and daemon using the commands at the server console:

rcsmb stop
rcsmbfs stop

If this resolves the problem and Samba is not needed, simply disable the service using these commands at the server console:

chkconfig smb off
chkconfig smbfs off

If Samba is needed, reconfigure Samba such that it is using a different name to advertise its service.

CIFS

Run iManager on the server where you are having the drive mapping problems, and under "Roles and Tasks" open "File Protocols" and then "CIFS". There, you will see the CIFS Virtual Server Name and whether CIFS is running on the server.

If it is running and the duplicate name is displayed as the CIFS Virtual Server Name, change the name to something else (usually, the servername with _W appended).

Feedback service temporarily unavailable. For content questions or problems, please contact Support.