NetWare MAP Command Does Not Connect to a Folder on a NetWare Volume

This article was previously published under Q229399
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you try to use the NetWare map command to connect to a folder on a NetWare volume from a computer that is running either Client Services for NetWare (CSNW) or Gateway Services for NetWare (GSNW), the operation does not work.
RESOLUTION
To resolve this behavior, use the net use command on computers that are running CSNW or GSNW to assign drive letters to folders on a NetWare volume.

You can use the following syntax to assign drive letter H to the SYS:Login folder on a NetWare server named NWSERVER1:
net use h: \\nwserver1\sys\login
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
The purpose of the NetWare map command is to assign a drive letter to a folder (Map.exe is located in the NetWare SYS:Public folder). For example, to assign network drive letter H to the SYS:Login folder on the NetWare server named "NWSERVER1," use the following syntax:
map h:=nwserver1/sys:login
Running this command assigns drive letter H to the folder, so that typing "h:" at a command prompt and then pressing ENTER connects you to the SYS:Login folder on the NetWare server named NWSERVER1.

However, after you run this command from a computer that is running CSNW or GSNW, typing "h:" and then pressing ENTER connects you to the root of the SYS: volume on the NetWare server named NWSERVER1.
Properties

Article ID: 229399 - Last Review: 01/05/2015 11:54:57 - Revision: 3.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbbug KB229399
Feedback
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)