Mapped Drive will not connect after reboot

Geoff, after much research, this worked for me. Correction, it did for a little while - see last line. Sigh

You need to allow anonymous access to your shares on the NAS.

Use gpedit to edit your local policy:

Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers

Set to Allow All

Computer Configuration > Administrative Templates > Network > Lanman Workstation.

Set Enable insecure guest logons to Enable.

Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options

Double-click Microsoft network client: Digitally sign communications (always) and set it to Disabled. Click OK.

I also went into properties for the workstations ethernet interface, selected Internet Protocol V4 properties, Advanced, and set Enable Netbios Over TCP/IP  to on.

Bad news edit: I was happily accessing the NAS shares finally, then I shutdown File Explorer and tried to access the mapped shares again. Timed out with reconnection error. OMG! I rebooted the workstation and tried to access the mapped drives in File Explorer - it worked. Shutdown File Explorer and retried. Timed out with reconnection error. What?

I'll have a look at this, the NAS (Thecus 4560) is set up for passworded access.   

What I've found is that many things seem to work.  Once.   Then a reboot or two later the issue reappears.

I tried something I found elsewhere in this thread, seemed to work.  Survived a reboot (without having to remap the drives this time, which is hopeful).   Mind you I'd restarted the NAS as well so it might be meaningless.  We'll see.

Add both these keys.

HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>CurrentVersion>Policies>System

add DWord (32bit): EnableLinkedConnctions  Set Value Data to 1

HKEY_CURRENT_USER>Network>Drive Letter 

add DWord(32 Bit): ProviderFlags  Set Value Data to 1

If there are no mapped drives, the Drive Letter Key (just a key folder for each drive letter with various parameters in them) won't exist.

I did it with the drives not working, didn't delete the mappings so the Drive Letter Keys were still there.   

Reboot.

I also noted the NAS hadn't had it's time zone set properly when it was installed some years back and NTP wasn't enabled either, so I've fixed that too.  Don't ask me how that was missed, but it's actually worked ok with Win7 like that for some years.   Go figure.  

The mapped drives all came up at once and actually work.   So I'm kinda hopeful.   We'll see how it goes over the next two days.  If it's still ok by Monday I think I might be on to something.   

Geoff

The SMB might be a way to the answer, as I had tick off SMB1, on my sons computer in order for it to connect to the old NAS, after it had been shut down for a longer period of time. I have not tried to connect to the new NAS on that computer yet, and I have not found anything concrete in regards to the SMB.

SMB 1.0 being present doesn't seem to fix it, though I think it helps.  (we needed it for other reasons to do with a PXE implementation on one of the workstations).   I'm reduced to pushing all the data back from the NAS to the workstation that I can and implementing backup regimes.   This doesn't eliminate the need for network connections or drives unfortunately, but at least they can get into their desktops, documents and mail reliably.  

I'm now trying to figure out how one of the WS seems to have magically changed the location path for Desktop to one for a different server???   Frankly they're not bright enough to have even tried to mess with this so not sure WTH happened there.  

I'm going to tinker with the NAS and do firmware upgrades today, not because I've any real hope it will fix it, but because I've got nothing else left to try.

IF Mr. MS is listening, this really needs fixing as a matter of urgency.

Cheers

Geoff

Group Policy Management | Default Domain Policy-Edit | User configuration | Preferences | Windows Settings | Drive Maps create new mapped drive -Action Replace - Reconnect ticked- make sure that mapping is targetted to the users that you need.

Turn off reconnect mapped drives at sign-in locally.

Now each time a user signs in the drives are mapped with no conflicts.

Ok, unfortunately this can't be implemented in a NON AD/Windows Server environment.   The issue is in an organisation that uses a Synology NAS and Windows 10 Pro workstations - no AD, no Domain Controller etc.

Thanks anyway, hopefully it will help someone out.   And word from anyone in the MS universe when/if this might be addressed?   The silence has been deafening.

Cheers

Geoff

Did the first of these some time back, doesn't seem to make any difference.  Still happens every few reboots.

The second key beyond Network doesn't exist ie no Drive Letter can you post a copy of your key?

Thanks

Geoff

Adding the following Registry Entries solved my problem.

HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>CurrentVersion>Policies>System

add DWord(32bit): EnableLinkedConnctions

Set Value Data to 1

HKEY_CURRENT_USER >Network>Drive Letter

add DWord(32 Bit): ProviderFlags

Set Value Data to 1

Thanks for that.

Doesn't help much, the end users are incapable of doing anything as complex as remapping drives, especially when their desktop didn't come up and they can't find File Explorer, so me taking a trip in there every 2nd day to remap it and slap it around more isn't working for any of us.

thanks

Geoff