Windows 10: NAS network mapping fails after update to windows 10 version 2004 or 2009

I have 3 NAS running in my private network:

1 D-Link ShareCenter DNS325, latest Firmware 1.05, no more update available


2 Iomega StorCenter ix2-200, latest Firmware 2.1.50.30227, no more update available


3 QNAP TS-251+, Firmware 4.5.1


I have updated 3 different PC’s to Windows 10 version 2004 and just a few days ago to Windows 10 version 2009. After the update the mapped network drives of the DNS325 and StorCenter ix2-200 which are much older than the QNAP TS-251+ won’t reconnect with either error “network path not found” or “the local device name is already in use”.


Essentially windows 10 version 2004 and 2009 do not recognize the 2 devices as NAS anymore and they do not appear under “network”.

I can however, access both by using a browser and type in their internal network address 192.168.1.xxx.


I have applied the registry modification described here: https://answers.microsoft.com/en-us...nnot-map/cf7eeb62-f794-465c-8693-7e543a907dae but to no avail.


Smbv1 is also enabled under “turn on / off windows features”.

I would be grateful to get a solution for this since I do not want to miss out on those important windows feature updates. Many thanks!

:)

 

Why is Windows 10 Version 2004 preventing logon scripts from mapping NAS drives at first logon attempt?

Since we updated Windows 10 to Version 2004 that all the machines in our domain stopped mapping NAS drives at first logon.

When the users start the machines and logon the logon script maps correctly the drives in several servers but not in the NAS.

If they logoff and logon again then the mapping is done correctly.

The problem occurs sistematically and started only after Version 2004 was installed.

It has nothing to do with SMB 1.0 being enabled - it was already enabled before Version 2004 as it was needed because we are talking about an old NAS.

Direct SMB appeared enabled and we disabled it, but it didn't solve the problem.

 

Windows 10 Update 2004

My system automatically maps a drive to a CIFS shared volume on my NAS. As of update 2004 when I attempt to access the network share Windows is unable to access it. This is happening on 2 PCs, both running Windows 10 Professional Update 2004.

I get around this issue by accessing the network share's web interface via Edge, using the NAS IP address'. Having then done that I can then manually map a network drive to the NAS volume via File Explorer. First I must disconnect the mapped drive and the
re-map it.

However, other users of these PCs are not as familiar with mapping network drives and this causes them to be unable to access important files and applications.

We had no problems with automatic mapping of network drives with Update 1909, but it is broken with Update 2004. Please advise a fix.

 

Mapping network devices such as NAS drives.

Dear Support,

I am having a massive problem with finding NAS devices on my network so I map them as network drives.

I had not changed any network configurations, but now I do not see my NAS drives in the list under "Network", nor can I map my NAS drives.

My previous mappings are fine and work OK. However, even the drives that were previously mapped that work OK do not appear in the list for the options of mapping network drives now.

I am running Win 10 latest version on an Intel 7th gen CPU, wired Ethernet.

I have checked to see that all my firmware is up to date, including router, NAS, network driver. I have checked that sharing is on, and turned off firewalls, made my network type private. I have searched every forum and technical note, and tried every video
out there, but I am at the end of my tether with this problem.

The problem seemed to occur after updating Windows. Everything was working fine before, completely flawlessly.

I am basically now completely fed up with the situation, and my only option left is to move all my computers to Linux. The problem has basically cut off access to data I need to work and is costing me money and time. I basically just want to cry as there
is no solution anywhere that I find. The Windows update has broken my network.

If anyone has any answers, please let me know.

Thanks for your time in advance.

Kind regards, Ben.