![mac network drive disappears after reboot mac network drive disappears after reboot](https://imgix-blog.setapp.com/gemini-scan-complete-similar-photos.png)
![mac network drive disappears after reboot mac network drive disappears after reboot](https://i1.wp.com/kcrack.com/wp-content/uploads/2019/04/SIW-Crack-Serial-key.png)
- #Mac network drive disappears after reboot update
- #Mac network drive disappears after reboot password
- #Mac network drive disappears after reboot Pc
#Mac network drive disappears after reboot Pc
This is in a school, and most of the teachers have only 5 minutes to log in on any available PC to get hold of their stuff, and have no time to recreate drive mappings first. If I then delete the stored drive mappings to NAS shares, I can recreate them just fine, but for most users it is a big hassle having to enter the network path and share names. Error messages like: Local device name is already in use' or 'Specified network names is no longer available' or (something like) 'Cannot log in with different user accounts' (varies). On 2004, it works OK with one mapping, to one share, but if you store 2 or more shares, there is no way to use those share-mappings next time you start the PC.
![mac network drive disappears after reboot mac network drive disappears after reboot](https://i.imgur.com/NCUIRrA.jpg)
#Mac network drive disappears after reboot password
After doing this for the first share, the other shares for the same NAS open without additional password entry. This works fine on 1909 - When users start their PC, they open the filemanager, click on the stored share name, and is prompted for the username and password for the NAS. When mapping drives for the first time, I tick the box for "Reconnect at Logon" (my windows is in Norwegian, so the wording might be a bit off). All our files, and log-in security, are on the NAS. All computers are common or non personal, with no user files stored on the local HDD. We do not have any domain, no MS accounts and no stored passwords. Our windows PCs don't have any passwords, and no profiles are stored. In Win10 p 2004, it works fine to map new drives, but reconnecting after reboot doesn't work. This works fine in Win10 P 1909 (and in Win7p).
![mac network drive disappears after reboot mac network drive disappears after reboot](https://support.fixmestick.com/hc/article_attachments/360001693974/2.MacBootOptionsefi.png)
All our users have at least 2 drive-mappings to shares on a Qnap NAS, most have 3, and some have 4 or 5 shares mapped. Now I got a new batch of laptops with 20H2 pre-installed, and I'm trying to fix this problem, without luck. So far I have circumvented the problem by installing version 1909 for the unlucky users (downgrading). I have seen this problem since we accidentally got 2004 on some PCs when 2004 first came out. Same problem here with Win10 P 2004 and 20H2.
#Mac network drive disappears after reboot update
Nothing changed at share(s), and all is totally OK when we try to connect either from a Windows 10 earier builds or Windows 7 clients, so the problem surely connects to a Windows update happened in august. After that, after a restart some shares are OK by IP, some by FQDN name, but when one is OK with IP it definiatelly fails with FQDN and vica versa. When we tried to change it to \\FQDN\share_name, on some windows instances it worked till the first restart: after that FQDN connections all failed, and when we retried with \\IP\share_name format, it worked. I connected a share earlier - before a restart - with \\IP\share_name format. The truth is, that network drives are present in GUI with red X sign, and when I click on it to try rebuild the connenction, a window appears with a message something like this: "Error to reconnect G: - Microsoft Windows Network: the local device name is already in use. " the network drives disappear in GUI (windows explorer) but you can check the drives are mapped with "net use" command. We have a same problem, but this opinion totally wrong: