Mapped Drives Issues

I am running Windows 10 Pro Version 1903 OS Build 18362.900. This is my home computer running in a work group. I have two NAS devices on the network. All of my home computers have mapped drives pointing to the two NAS devices. All of the computers except my main machine have no issues with the mapped drives.

On may Main machine the mapped drives would never reconnect when I booted the machine. The drives would appear windows explorer's left hand frame with a red X. If I clicked on the either of the two drives, Windows would pop-up a message saying there was an error reconnecting but then would proceed to connect and display the drive contents in the right hand frame of Windows Explore. After that the red X would disappear and they would function as normal.

Two days ago Windows explore stopped displaying the mapped drives. I can ping the drives. I see the drives under the network tab. If I right click on the NAS drive and then click open the drive folders display in Windows Explore. If I try to re-map the drives, Win Explore says they are already mapped and displays them in the mapped list. If i use the "Net Use" command it displays the two mapped drives indicating that they are already mapped. I've tried the "disconnect network drive" option and then re-added the network drives.

I still can't get the drives to list in the the left hand drive list in Windows Explorer. It's a real pain to go thru the network devices -> right click -> open sequence every time I need to access the NAS drives.

How can I fix this issue?

Welcome to the forum. How are you mapping the drive you need to use /persistent switch so it will keep the settings

I used the Windows Explore Map a drive function and selected the auto reconnect at Boot function. I only used the Net use command to see the status of the map drive connections.

SMB1 is a security risk.

https://techcommunity.microsoft.com/...b1/ba-p/425858

If you have to use it because a device on the network doesn't support SMB2, use SMB1 client only.

storageman said:

I've noticed the same problem. I assume your main machine is pretty fast ? If it is than W10 tries to re-connect to the network drive, but if fails it just moves on. I wrote a little .cmd routine that retries forever when it fails to connect, but when it does connect, it exits and issues a console msg that it connected OK. It does display the message when it fails.

PM me on TenForums here with your email address and I'll send it to you with some doc that explains what it does.

I tried a PM on this forum but it appears that as a new member I am not yet authorized to access the PM function.

- - - Updated - - -

Ztruker said:

Check that SMB1 client and server are enabled:

Open Control Panel.
Click on Programs and Features
Click on Turn Windows Features On or Off
Scroll down to SMB 1.0/CIFS File Sharing Support and expand it (click on the +)

Check SMB 1.0/CIFS Client
Check SMB 1.0/CIFS Server

Click OK

That feature will be installed, which takes a minute or so.

I have relatively new NAS devices that both support SMB 2.0 so this fix doe snot solve the issue but thanks for trying.