Windows 10: Looking for help for a network connection issue with Windows 10 / 2004 Mapped Drive

My network typically has 3 to 4 Windows 10 computers connected and 6 or more from time to time. Also there are 3 D-Link NAS Mapped. Two are DNS-323 and these are working fine and one Sharecenter DNS-345, the one I am having issues with.


All the computers were working without network issues when they were all version 1909, but two were updated to version 2004. Here is where the problem started. When the computers with version 2004 boot up, they do not re-connect to the Sharecenter DNS-345, but do re-connect to both of the DNS-323 NAS. I have found that I need to disconnect the unconnected NAS in Windows and re-add it. This in itself is an issue, because it typically is seen in the network connection window, but it is not accessible. I then use the IP address and sometimes when the window opens the address is there and sometimes it is not. But then the NAS might be accessible though the name or not. Trying again might have the address show up and then the network name might be accessable, but for sure I am able to connect via the IP address.


Unfortunately, no matter whether I connect via IP address or Network Name, upon reboot of both of the computers with version 2004, they do not re-connect to the Sharecenter DNS-345. Back to square one and removing the mapped network drive and re-mapping it. My network was bullet proof and I haven't had any issues since the issues with the Windows release from a couple of years ago. That I got around easily. This is frustrating me and I don't find any web chatter about this problem. If I could go back to version 1909 I would, but I believe that option is off the table. Can you help?


Thanks, Gary .

:)

 

Map Network Drive in Windows 10


thank you for doing this tutorial.
An issue that plagued us in earlier Windows still remains in 10 and I do not yet understand some of the solutions given in the superuser forum thread pasted below.
The issue is simple:
- "drives" are mapped correctly, and work well WHEN they are manually accessed.
- Windows 10 automatically disconnects the resource when not used.
- Waking or restarting/booting the mapped drive remains disconnected: no request has been made, therefore the shared resource is offline [Red X]

the solution would be something to cause the mapping to be ready/available/connected at all times except for sleep [I guess... that would be permissible to most] or 'off'. In the thread below a couple of people propose 'solutions' [despite a couple of boneheaded ideas] but these either over-reach or are limited only to solving the 'connect at startup' need.

Not solving this defeats automated routine backups [pushed from the client station in question, in this example], which can be deadly. users should not be expected to have great memories or great technical skills

what is the RIGHT step to take to make the Mapped resource "always available", with exceptions noted above?

On login, how do I get Windows to mount/connect a mapped network drive automatically? - Super User

 

Version 2004 network issues when drives are mapped

Thanks I’ll give it a go. It’s weird because this never an issue til the 2004 feature update. Is there a way I can set a drive to be mapped to Y as part of the login process. Because if once logged in I then map one of these drives then they work ok and are not inaccessible but the problem immediately returns on next restart. So to workaround I can temporarily map them but always have to disconnect them on shutdown

if a CMD can be set to somehow run automatically on login that disconnects at the end of my session when shutting down that could be ideal

baffled why the true NAS drives seem fine and this only afflicts the USB hard drives connected to the router USB and another connected to an access point

 

Permission issue, shared drive Windows 10.

Hi,

Thank you for writing to Microsoft Community Forums.

We can understand your concern. However, we would need some more information regarding the issue.

1. May I know the exact error message?
   
2. Have you shared all hard drives or any particular folder within the particular hard drive?
   

Since you have mentioned that you are getting error related to permission issue, please refer to the troubleshooting steps provided by “Azee N” dated June 2nd 2010 on
Providing permission to drive and try
providing permission to the drive.

If the issue still persists, we would suggest you to follow the steps mentioned below to re-map the drive.

1. Disconnect the drive by right click on the drive and select disconnect (if the drive is mapped).
   
2. Then re-map the drive by referring to Map a network drive
   and check if it resolves the issue.
   

Regards,