Windows 10: Every time I reboot my mapped network drives become inaccessible

I have a Synology Diskstation DS220j with multiple network share drives allocated that I have had mapped to drive letters on my PC. After the recent Windows 10 updates last week, every time that I reboot my PC, the mapped drives become inaccessible. All of the drives still appear in This PC, and show the green status bar indicating that they are connected, but when I click to open the drive I am met with "An error occurred while reconnecting <drive letter> to <domain address> Microsoft Windows Network: The local device name is already in use". The only remedy that I have been able to find to access the drive is to unmap all of the drives and then remap all of the drives. As a side note, the process of unmapping the drives is long and tedious, because Windows Explorer hangs for a couple of minutes every time I try to interact with these mapped drives. Once this is completed, I am able access these network drives without any issue at all....until I restart my PC, and then the whole process begins again. I have poured through online forums and found multiple "fixes" for this type of issue over the past several years, but trying these has yielding no viable solution. Does anybody here have any suggestions?

:)

 

Version 2004 network issues when drives are mapped

Hi, I’ve got quiet a few access points and switches dotted around. Couple of NAS drives. These work great. I map them as drive letters and all works great. Diff story for a couple drives connected to access point and router’s USB port. If I map any folder on these drives they become inaccessible on next reboot. They are also inaccessible in the network. But as soon as i disconnect the mapped drive then they are no longer inaccessible under network. I can click and broaden the contents just fine. Anyone notice the same? Mapping a drive on anything other than a true NAS drive seems to have these side effects

 

Trouble Mapping Network Drive

I have a WD NAS drive connected to my router and have mapped it on three of my computers. I just setup another laptop with Windows 10 and have updated it to 1809 and when I tired Mapping a network drive nothing is displayed in the browse window except the
computer I am currently using. The drive is shown under network locations in File Explorer but not when you select map network drive and browse. I right clicked on the drive and selected properties and noted the IP address and went back into Map network drive
but instead of selecting browse I entered the IP address but it still does not map the drive. The strange part is if I go to any of the computers that already has the network drive mapped and select Map network drive and select browse none of those computers
show the drive either but you can select the mapped drive in the drive list in file explorer and it works just fine.

I have read several articles both here and elsewhere and tried the suggestions but nothing works. Network discovery is turned on as is file sharing and also checked if all three boxes under SMB file sharing support in Windows features were also checked and
they are. I have mapped several computers to several different drives over the years and anytime the drive was not listed it was always easy to go into Network Sharing Centre and find the problem but everything seems to be as it should so would appreciate
if someone can suggest something I may have overlooked.

Thank you

 

Mapped Drives Issues

To clarify .... the issue is the Windows 10 OS. It is with Windows File Explorer. The Mapped drives used to appear in File Explorer's left panel list of drives and folders. Two days ago File explorer stopped show the mapped drives. so not they don;t appear in the list of Drives and folders.

- - - Updated - - -

I did, it has no effect. I also check the NAS devices they support SMB 2.0. Also I have several other computers on my home network they work fine with the mapped drives and They do not have SMB 1 turned on. So it is something that happened to the computer in question.