Windows 10: File explorer not responding due to mapped network drive not connected.

Hi All,I have mapped network drives, which are only available when my laptop is connected to certain networks work, VPN. When I open file explorer and mapped drives not are not accessible in my current network, then it's very slow to open the "This PC" view, and the progress bar just keeps loading in the address pane. This also tends to entirely lock up file explorer, such that I'm unable to open other explorer windows.Is there any setting on OS level if mapped network drives are not accessible than its stopped receiving in backend after some seconds.Regards,Sid

:)

 

W10-32 explorer stops responding on mapped drive access.

If I wait long enough ... several minutes, it seems to access ... finally. Copying files from mapped drive ... same thing ... stops responding but wait long enough and it happens. No such problems with other machines on network. No such problem in the past (worked fine at one time).

W10-32 v. 1909 Build 18363.535
Network drive mapped to M:
DISM and SFC routines to not reveal any problems.

Now, it gets really weird. UNmap drive. Open Explorer. Network drive not found under NETWORK, but still shows as a mapped drive. See screenshot.





I really don't think this is right. If UNMAPPED .. should not show this way. It should show in NETWORK since it is shared. If I click on it as shows AS mapped, Explorer opens it, and it does not stop responding. Access to the drive works perfectly.

Any help is appreciated in advance.

EDIT: Fixed it.

1. Correct file corruption with chkdsk /f
2. Follow the steps below:

Go to gpedit.msc
Under Group policy editor access the following :-
->Computer configuration\administrative templates\network\Lanman Workstation
->"Enable insecure guest logons"


#Go to services.msc
The following should to set to Automatic[Delayed Start]
->Function Discovery Provider Host
->Function Discovery Resource Publication


#Go to Programs and features
Under Turn on Windows Features
->SMB-1.0 File sharing and support all three items should be enabled.

Thank you Netgear Gearhead support.

 

Connecting NAS - mapping of drives

Ok,

If you want, we can do a step by step troubleshooting of your current situation:

If you are able to ping your Machine and it responds.
Code:

Try to view if your NAS appears on the Network List:
Code:

If Your NAS appears on the list, try to view it:
Code:

The available shares will be listed there.

Then Try to List the content of one of the directories:
Code:

This should list the content of the directory,

If all this works Try to map a drive on one share:
Code:

Pls reply with the "response" of the first "encounter" of a non positive output.

This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.

 

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