Cannot map network drive due to "System error 86"

[tygr]

I apologize if this is a stupid/frequent question but I couldn't find this exact issue on the forums or honestly anywhere; maybe I just don't know what to look up.

I setup my DS920+, made user accounts, created shared folders, applied privileges, etc. For example, let's say I created the user named "Main" with the password "Password". I try to map the shared folder to a network drive in Windows 10, and it asks for credentials. I put in the username "Main" with password "Password" and it says invalid password. I attempted [net use v: \\deviceIP\sharename] and login via the username and password, and I receive "System error 86 has occurred. The specified network password is not correct." I get the same issue if I use the Synology Assistant.

I can log onto the DS920+ just fine via the DSM through my web browser and I can ping the device in Windows just fine. I am not part of a domain. I've tried adding the windows credentials to no luck. I've cleared windows credentials and restarted to no luck. I'm very new to this but I've spent the past couple of days trying to research this issue and haven't come to any solutions that work for me. Can anyone point me in the right direction? Thank you.

 

[EAZ1964]

In my experience this is most probably a WIndows issue.
Best to sesrch the forums with keywords like connection issue nas.
You will find several guidelines how to solve this, like flushing dns cache, correcting security settings in registry etc. Sometimes a reset of the W10 network helps.

 

[ed.j]

Do you need to enable SMB for that user?

Control Panel -> User -> (select user) -> Edit -> Applications -> SMB allow

?

 

[tygr]

Do you need to enable SMB for that user?

Control Panel -> User -> (select user) -> Edit -> Applications -> SMB allow

?

This user has all applications allowed.

 

[EAZ1964]

> Run as admin
> Copy paste each of the Following commands + Enter for each
ipconfig /flushdns
netsh winsock reset
netsh winhttp reset proxy
netsh winhttp reset tracing
netsh winsock reset catalog
netsh int ip reset all
netsh int ipv4 reset catalog
netsh int ipv6 reset catalog

otherwise:

How to Reset Network Settings in Windows 10

If you learn how to reset network settings in Windows 10, you can use the network reset utility to resolve network connection issues much easier.

www.lifewire.com

An NAS drive not visible , error occurred while reconnecting in Windows 10

NAS ( Network-Attached drive ) is a file storage solution that acts as a server for multiple LAN connected computers where the computers can use NAS as a virtua

thegeekpage.com

4 Fixes When You Can’t Map a Network Drive in Windows 10

Mapping a network drive has many benefits, especially if you want to transfer files using a network faster. If you can't map a network drive, Windows 10 has a simple solution we’ll cover in this post. Creating a shortcut to another folder or drive shared on the network means you are mapping its...

helpdeskgeek.com

 

[fredbert]

Just to be 100% certain: you have allowed the user to access the new shared folder?

Can this user connect to their home folder from Windows? \\NAS\home

 

[tygr]

Just to be 100% certain: you have allowed the user to access the new shared folder?

Can this user connect to their home folder from Windows? \\NAS\home

If I do this, it just gives me invalid password. Upon performing a windows "diagnose" it says I do not have permission to access. If I log on to this user via the DSM, I can access the shared folder.

 

[fredbert]

Which version of SMB are you using?

 

[EAZ1964]

if you seach the error 86, it may well be as easy as setting NTLM to NTLMv2

Use the local security settings to force NTLMv2

On this page:

kb.iu.edu

 

[tygr]

Which version of SMB are you using?

I'm using Max SMB3 and Min SMB2. On my Windows machine, SMB1 is enabled and SMB2 is enabled.

-- post merged: 1. Dec 2021 --

if you seach the error 86, it may well be as easy as setting NTLM to NTLMv2

Use the local security settings to force NTLMv2

On this page:

kb.iu.edu

I'm currently on this setting. Changing to NTLMv2 response only prevents me from connecting to the NAS entirely via my Windows machine, whereas I still get error 86 when on Use NTLMv2 If Negotiated.

 

[Telos]

If I do this, it just gives me invalid password. Upon performing a windows "diagnose" it says I do not have permission to access. If I log on to this user via the DSM, I can access the shared folder.

That can simply be a credentials conflict. Delete all credential which apply to your NAS. Reboot PC and try again.

 

[EAZ1964]

View attachment 4938
I'm using Max SMB3 and Min SMB2. On my Windows machine, SMB1 is enabled and SMB2 is enabled.

-- post merged: 1. Dec 2021 --

View attachment 4939
I'm currently on this setting. Changing to NTLMv2 response only prevents me from connecting to the NAS entirely via my Windows machine, whereas I still get error 86 when on Use NTLMv2 If Negotiated.

SMB settings look fine. In case the NTLMv2 does not work, check the NAS side first, it is in SMB “advanced, Other”. In case that is ok (NTLM v1 not checked) there is definitely a W10 issue, as NTLMV2 should work, it replaced the vulnerable v1 several years ago.

 

[tygr]

SMB settings look fine. In case the NTLMv2 does not work, check the NAS side first, it is in SMB “advanced, Other”. In case that is ok (NTLM v1 not checked) there is definitely a W10 issue, as NTLMV2 should work, it replaced the vulnerable v1 several years ago.

NTLMv1 is not checked on the NAS. I figured it wasn't the NAS as I've had similar issues to this some time ago with an old DIY NAS, but I just can't seem to fix this one. I'll do some more research on the Windows side of things.

-- post merged: 2. Dec 2021 --

That can simply be a credentials conflict. Delete all credential which apply to your NAS. Reboot PC and try again.

There are no saved credentials on Windows besides the generic ones.

 

[dglp]

Lots of good info here - am having problems of this sort, so will make my way through the various suggestions.

Seems clear that there are several things that may contribute to the issue, so I'm hoping there's an extended, step-wise list of things that can be checked and eliminated. I might start such a thread if I solve the problem without reformatting my NAS drives.