Novell Home

My Favorites

Close

Please to see your favorites.

Error when attempting to unmap a drive mapped via 'net use' command

This document (7014568) is provided subject to the disclaimer at the end of this document.

Environment

Novell Client 2 SP3 for Windows
The same username and password is used for both eDirectory and Windows logons.

Situation

When trying to remove a drive mapped via the 'net use' command, an error appears:

You currently have files open on <drive> (connected to <path>). If you
don't close the files before disconnecting from the network device, you might
lose data. Do you want to disconnect?

Answering 'yes' to this prompt does not disconnect the drive and produces a new error, and the drive stays visible in the "Computer" view of Windows Explorer:

This network connection has files open or requests pending.


The specific steps to duplicate this issue include:

1. Login simultaneously to Windows and eDirectory tree with same username and password.

2. Use "NET USE X: \\server\volume /PERSIST:YES" to map a drive to an OES NSS volume. Issue does not happen with drives being mapped from the eDirectory login script.

3. Reboot, and login again to both eDirectory and Windows from the Novell Client credential provider.

4. From the "Computer" view in Windows Explorer where all the local and currently-mapped network drives are shown, right-click and select "Disconnect" on the persistent drive map.

Resolution

The fix for this bug has been released in the following patch:

Novell Client 2 SP3 for Windows (IR6) http://download.novell.com/Download?buildid=hRPJ_OZQsIw~

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7014568
  • Creation Date:13-FEB-14
  • Modified Date:27-FEB-14
    • NovellClient

Did this document solve your problem? Provide Feedback