Novell Client 2 SP3 for Windows
When mapping drives in the login script using the "MAP *n" syntax (e.g. MAP *1:=MYSERVER\SYS:) the drive mapping fails with the error:
LOGIN-LGNWNT32-400: A network drive cannot be mapped to a drive that is designated as a local drive.
Replacing the "*n" with a drive letter allows the mapping to success as expected.
Examining the entries under "Hard Disk Drives" in Windows Explorer displays both "Local Disk (C:)" and "Local Disk (Z:)" where both show the same free and total space.
Disk Management displays only one disk, (C:).
General: Locate the application or process that is mapping the Z: drive.
Specific: Remove or reconfigure the UniPrint application.
To temporarily correct the problem:
1) Verify that UniPrint is using the Z: drive
- At the command prompt, type the command "SUBST" You will see output such as
Z:\: => C:\<path>
2) To remove the substition, type this command: "SUBST z: /d"
To permanently correct the problem, change the UniPrint configuration:
1) In REGEDIT.EXE, navigate to \HKEY_CURRENT_USER\Software\UniPrint\Client
2) Change the "PreferredVirtualDrive" from Z:\ to the drive letter representing the first available drive letter on the system. e.g. If the local hard drive is assigned C: and the DVD drive is assigned D:, you might assign E:\ to the UniPrint client.
Note: Different versions of UniPrint may have different configuration requirements.
The Z: drive is already assigned as a local drive, either by an actual device (such as a USB drive) or some process or application is assigning the drive.
When assigning drives using the *n (next) syntax, the Novell Client detects that the Z: drive is already allocated as a local drive (such as a USB flash drive). The Client starts from Z: and works down to find the first local drive it encounters (usually D: or E:), then allocates the next drive. Because Z: is found to be a local drive, the process stops as soon as it begins.