As a consequence to this, we decided to create this article in which we show you how to create a drive mapping in Windows Vista, 7, 8 and Windows 65. As you will see for yourself, the procedure of creating a map drive in Windows is very simple. For those of you who don't know it, a drive mapping is a letter assigned to a disk or drive.
It may not fix yours and is more likely to work with laptops.
For example, you can use the letter Z: to refer drive C: or a network server or a specific shared folder to which you have access to.
In Windows 7 and 8, click the File Explorer icon from your taskbar and then click the Computer link from the left vertical navigation bar.
The most common drive mappings are A: for the floppy disk and C: for the primary hard disk.
Just follow these steps: In Vista, first, click on the Computer shortcut from your desktop or from the Start Menu.
Could it be something on the server causing network shares to disconnect from everyone?
(it's good practice anyways and who doesn't like a good cable run).
7) Check the power settings as mentioned in the post by Victor7655.
My case is that we have about 5 users on the network that it is happening to and it is all the same shares from only one server.
One of the most searched topics on our site is how to map a drive.
I have a handful where the drive mapping just disappears during the course of a day.
6) Check the cabling run first as suggested by John White and Elgin8999.
I recently deployed a new Server 7567 R7 with a single share to about 655 users on a similar amount of computers.
If you are on a network, a drive mapping can reference remote drives to which you can assign a letter of your choice. In the toolbar you will find several buttons, including one called Map network drive. Unfortunately, until now, the searches on this topic didn't return any result for our users. If you have tried the above troubleshooting steps and are still having issues, I would suggest to open your own thread in the community to get fresher troubleshooting ideas. Could it be a switch going bad somewhere in our infrastructure?