Click here to Skip to main content
14,838,162 members
Articles / Operating Systems / Windows
Tip/Trick
Posted 23 Aug 2020

Tagged as

Stats

3.8K views
3 bookmarked

Finding my Network Shares on SMB1 Drives after the Windows 10 2004 Update

Rate me:
Please Sign up or sign in to vote.
5.00/5 (1 vote)
23 Aug 2020CPOL
Windows 10 and the ongoing "I can't find your mapped drives anymore" problem. A fix, hopefully!
It's a PITA: you upgrade to 2004, and suddenly Windows can't find your drives anymore. If, like me, you generally use mapped drives onto your NAS suddenly losing them can be a real problem - enough to make you revert back to the previous OS version. And it seems to be a change to support (or the lack thereof) for SMB1 devices. We can't all upgrade our NAS devices or their software (and in my case, Seagate support haven't even got back to me after over a week) so we need a workaround. This provides two, one worked on my Desktop (most of the time) but not on my Surface (except occasionally) - but together, they seem to fix the problem.

Hosts File

This is a "lookup" that the OS grabs at startup and uses to map domains to IP addresses quickly.

So first off, set your NAS to a static IP LAN address - that'll be up to you to do as it's specific to each router, I can't help you with that unless you have exactly the same router I do (TalkTalk SuperRouter, a badged Huawei HG635 I believe).

1) WINKEY, then type "notepad" - right click and select "Run as Administrator"
2) Accept UAC
3) Open the file "%systemRoot%\System32\Drivers\etc\hosts" 
4) Add your mapping: "192.168.0.11 \\SGNAS #Seagate BlackArmour 16TB" is mine:
      IP first, then at least one space 
      Domain next, I use the \\ prefix but I'm not sure it's needed. (If it ain't broke ...) 
      Anything after "#" is a comment.
5) Save the file and close Notepad.

Image 1

Regedit

Despite having \\SGNAS in my Hosts file, my desktop is fine, but my Surface keeps losing SMB1 devices completely, via IP or domain name.
This was getting frustrating ...

Then I found this - ProviderFlags ([Samba] Re: msdfs root problems even after a reboot? and it seems to be working so far:

1) Open Regedit and accept UAC.
2) Navigate to HKEY_CURRENT_USER\Network
   You should see a list of mapped drives as individual twigs:
       A
       B
       M
       P
       S
       V
       W
       X
3) Open each drive twig and add a new DWORD32 Key named "ProviderFlags".
3.1) Set the value to 1 (you can just press ENTER to open the edit box once it's highlighted)
4) Reboot.

Image 2

Points of Interest

With the domain / IP mapped in Hosts and the regedit mod, all seems fine and indeed considerably faster than it was before the 2004 upgrade!

History

  • 23rd August, 2020: First version
  • 23rd August, 2020: Removed <code> ... </code> from blocked text.
  • 24th August, 2020: Added images

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

OriginalGriff
CEO
Wales Wales
Born at an early age, he grew older. At the same time, his hair grew longer, and was tied up behind his head.
Has problems spelling the word "the".
Invented the portable cat-flap.
Currently, has not died yet. Or has he?

Comments and Discussions

 
QuestionDon't do this Pin
atverweij24-Aug-20 5:55
Memberatverweij24-Aug-20 5:55 
AnswerRe: Don't do this Pin
Dave Kreskowiak25-Aug-20 9:56
mveDave Kreskowiak25-Aug-20 9:56 
QuestionMessage Closed Pin
23-Aug-20 20:17
Memberlenoxtons2023-Aug-20 20:17 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.