Skip to main content
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.

Unable to Map Network Drive: Currently Mapped With Different Username/Password


When doing a Smart Console install or troubleshooting an issue, you may come across this issue when trying to map drives to Smart Suite or when Smart Console attempts to map the drives automatically. This article will explain and provide a few different ways to resolve this issue.


2019-01-29 14_17_33-C__WINDOWS_system32_cmd.exe.png

unable to map netwrok drive.png

2019-01-29 15_36_44-Command Prompt.png


In this specific example, Smart Console (wpkg-download.bat) is having an issue mapping the Z: drive to the wpkgclient share on the spokwb01.wpkg server, but these steps can also help with other network drives when getting a similar error.

When getting this specific error, it usually means that there is already a network drive mapped or a network location accessed from the computer to the same location you are trying to reach.

1.)  First step is to manually close and disconnect any network drives currently mapped to the Smart Suite system and try mapping the drive again. 

2.)  If that does not work open the command prompt and run the following command: net use

a.)  This command will output a list of network drives and locations currently active.

2019-01-29 15_47_42-Command Prompt.png

b.)  Sometimes within Windows, network locations can be cached even if you close the connection. 

c.)  To remove the connection you run the following command: net use /delete <network location>

i.) In this specific example, non-network drive, command would look like this: net use /delete \\spokwb01.wpkg\wpkgclient

ii.) If you need to remove a mapped drive, such as the X: drive above, the command should look like this: net use /delete X:

d.)  After they are removed, try and map the drive

3.)  If you are specifically having issues mapping the wpkgadmin and wpkgclient drives, it is important to note that both of these shares access the same exact folders on the Web Server. This means that if you are having an issue accessing wpkgclient, and have removed all connections to wpkgclient, you may also need to remove connections to wpkgadmin.

4.)  If none of the above steps works to resolve your issue, reboot the computer and test mapping the drive on startup. This should clear any of the temporary network locations that were accessed. If it does not work after that, then the issue may not be related to this error or there is some other network drive causing the issue.

Other Troubleshooting Steps 

If having issues mapping drives not specifically related to the error above, here are a few common issues that can be looked into to help resolve the issue:

1.)  Verify server that you are trying to access to be sure that it is valid and there are no spelling mistakes

2.)  A good step to take if automatic mapping is not working, is to try and map the drive manually in Windows. If you receive a network related error, it may indicate that you do not have network access to that server, a required version of Samba has been disabled, or Samba is not configured to make connections outbound.

a.)  If using Smart Suite 4.x or 5.x, ensure that Samba version 1.0 as not been disabled on the computer. Due to the requirements on the servers, Samba version 1.0 needs to be enabled and working on the local workstation to be able to map network drives to the Smart Suite servers.

b.)  In some instances, the Samba configuration on the server can be setup to only allow certain workstations by IP address to connect to it and will block all others.

Related Defects: