A mapped network drive is a drive or a folder connected to a computer that is being shared from another. The one sharing is called the “server” even though it’s not always an actual server and the computer mapping the drive is called the “client”. Most networks have a server sharing out a “Data” drive that all the workstations map. Different issues arise with these connecting from time to time, usually indicating the source of the drive (the server) has gone offline. If you can open the drive in Windows Explorer, the drive is currently connected and working. If there is a red “X” on the drive or it never opens, try the following steps.
On the client computer, Run =>
\\ServerComputerNameto see if it can read the shared files. If this returns a
Network Path Unavailableerror, see One Workstation Won’t Connect To the Network. Make sure to complete those steps first.
If the drive is mapped and asks for credentials when you open it, you need to add the credentials from the client to the server. Example: I am logged in on a workstation as
user\12345. The server needs to have a local user with the same exact credentials in order for the mapped drive to work. You will need to get on the server computer and add your user info to its list of users. To do this, Run =>
compmgmt.msc=> local users and groups => users => add user => enter your info. You cannot have the same user name with different passwords, it will not work. If you are on a workgroup with all users the same name, they need to have the same password if they are all mapped to a single shared folder/ drive.
Make sure the server computer is sharing out with full permissions if you want all computers to connect to it or make sure all client users are in the correct group that has “Read” access to the folder/drive. Really, they should have “Full Control” so that each user can read/ write/ modify files on this drive/ folder.
If it’s still not working, look at the Windows Time. Go to time and date settings => internet time => and change time.windows.com to any of the others. This gets bogged down sometimes and can get tampered during networking issues.
Check the link speed of the client computer to the server computer. Run a series of pings to determine if they are able to communicate at normal speeds, should be >1ms or so.
Once the issue is resolved, on the client computer, right click on the drive and “Disconnect” it (if it was previously connected), then Run =>
\\ServerComputerName=> Right click on the drive => Map Network Drive. Enter the login credentials for the server computer and remember to check the “reconnect at logon” and “remember my credentials” boxes.This will re-add the drive with your new credentials.
To Use A Batch File For Startup:
- Should look like:
net use m: \\ServerComputerName\d_drive /persistent:yes
- where “server” is the server computer’s NETBIOS name and “d_drive” is the name of the folder/drive being shared. Note that the letter “m:” plays no significant role.
If A Mapped Drive Doesn’t Want To Delete:
run => cmd => Type:
Net use n: /delete# where n is drive letter. Use
\*to delete all mapped drives at once, ex Type:
net use \* /delete
If that doesn’t work, Run =>
Regedit=> Navigate to:
You will see
\\ServerComputerName\sharesubfolders. Delete the folders you don’t want and reboot.
----------------------------------------------------------- Spotted a mistake in this article? Why not suggest an edit! -----------------------------------------------------------