Synology password not recognized on Windows - mapping impossible
Pauvreblaireau Posted messages 13 Status Membre -
Hello, After a Windows 10 and 11 update (2 computers) and an update of the Synology NAS SMB, the latter is no longer accessible from the Windows Explorer: The system keeps asking me for the NAS password, but it won't accept it. Yet, this password is correct, and to check, I created other accounts with different passwords in the NAS and none work from the Windows Explorer, while they all work through the browser. So I can no longer map my folders, even with the Synology assistant, whereas it was working perfectly before the updates. I have tried everything, checked the SMB settings in Windows and on the NAS (SMB 2 and 3), I deleted the Synology entries in the credential manager, checked access permissions and network discovery, etc... I have tested all the methods proposed in the forums. I even disabled SMB1 in the Windows registry, to no avail. So now I am completely stuck, and it's really frustrating! If anyone has an idea, I thank you a thousand times in advance!
9 réponses
Hello,
Rather than testing with Windows Explorer, it's better to use "net use" in a command prompt: this provides (slightly) more explicit error messages.
Microsoft regularly removes options from the SMB protocol to reduce security risks. To do this, Microsoft partially modifies the SMB software and partially changes the default values of the SMB options. These options can be controlled via "Local Security Policies", which is not installed by default in the Home versions of Windows.
Hello,
can you connect to other network shares than the NAS?
Can you revert back to the previous Syno update?
And there you go, there it is ....
But misery, the line spacing is so annoying!!
Yes, I can access the hard drive of my Freebox without any issues, but I haven't tried accessing the other PCs on the network yet; I'll try to do that as soon as possible. I tried to revert to the previous version of SMB, taken from the download pages of the Synology site, but it didn't work, and whenever I reset the NAS, the latest version of SMB is always installed.
Hello,
What version of DSM are you on? I just saw that there is a DSM 7.2 version. On my newest NAS, I'm on DSM 7.1.1-42962 Update 6 and to upgrade to 7.2, I would have to do it manually, as it's not supported by the automatic update.
Here are the mantras of 7.2
Immutable storage and backup, fast encryption of full volumes, and stricter access controls. The new DSM allows you to transform your system into a true data fortress.
So it is likely that access controls are strengthened, with new settings.
But this could also come from Windows. We have already seen that some updates could change parameters like SMB.
Hello Jee-Pee,
I reset my NAS and during the reconfiguration, it automatically downloaded version 7.2.2-72806. My Synology DS218 is therefore on the latest version of DSM.
If my NAS has become a fortress, it shouldn't prevent access for its own administrator!
Joking aside, I set all protections to a minimum, so when I connect via the browser, it obviously tells me that the site is not secure and that I should think twice before connecting! Regarding the Windows settings, I've checked everything, at least everything that was already suggested in other posts, like removing passwords from the credential manager, the version of SMB, enabling network discovery, disabling the guest account, network settings, etc..
By the way, the Synology icon appears twice when I click on network in File Explorer, once as "other device" and a second time as a computer. Clicking on the Synology "other device" icon opens the Synology connection in the browser, and when I click on the Synology "computer" icon, it opens a username and password login window. It's this box that refuses to accept the username and password for my Synology, even after changing them several times in case some characters in the password were poorly "digested" by Windows... Each time it responds with invalid username or password. I also want to clarify that I created several accounts with rights on my Synology, but none have been able to log in... Maybe there is an incompatibility between the latest Windows update and the latest version of SMB, in which case Synology urgently needs to address this!
(PS: I also tried uninstalling the latest Windows updates, without success, the connection still did not work)
Thank you all for your responses, that's very nice,
For SATS_fr and Kaumune, the fact that you haven't had any issues with the latest Syno and Windows updates and that you can map your NAS reassures me, so it seems there are no bugs or software incompatibilities, it's with me that things are going wrong, so I will continue to look into certificates and such.
For yg_be, I am using the pro version of Windows 11. I've already modified quite a few SMB options but I will take your advice and go through net use.
This story is still strange because my NAS works perfectly, it accesses the internet for updates and other things, and on my side, I can access the entire NAS via the SMB web interface, the same goes for my videos and photos that I can play without any problem from my Free player (after entering the username and password of course, and it works) which proves that the network is functioning.
The only thing that doesn't work is that my credentials and passwords are systematically rejected under Windows, even after resetting the NAS and reinstalling SMB, having opened and closed multiple accounts and updated the credential manager each time. And of course, I can't map the folders and thus I don't have direct access to my files from Windows.
My other PC running Windows 10 pro also refuses the connection. I have a laptop running Linux that I don't use much anymore, but I will bring it back into service and see what it does.
To be continued...
Through the browser, Windows does not use the SMB protocol.
It's also useful to perform a test (net use) with an incorrect user or password to check that it gives the same error message as when everything is correct. By varying the error conditions, it sometimes allows us to obtain more information.
Net use behaves the same way whether I enter a valid username or password or an invalid one: system error 1326 has occurred, the username or password is incorrect. In short, it's exactly like the login windows in the file explorer. It feels as if I'm consistently making a typo, no matter the username and password since I've created several accounts on my NAS and then deleted them, and each time after clearing the Windows Credential Manager.
I'm thinking of something: is the NAS set to the correct time, is it synchronized with the internet (NTP)?
This is important on a domain, but I assume you're in a workgroup; however, it's likely that the NAS is master browser or trying to be one above all.
Well friends, thank you all for your responses.
I just solved my problem thanks to the page https://kb.synology.com/fr-fr/DSM/tutorial/I_cannot_access_shared_folders_from_WinXP_computer
Initially, I enabled NTLMV1 and then I was able to map my NAS and assign virtual drives to each folder in Windows Explorer. Then I followed the advice from the link above, namely in secpol.msc to enable NTLMV2 exclusively, prohibiting LM and NTLM.
I also restored all the security settings that I had turned off during my searches (access blocks, firewall, etc...).
Phew!!!
The authentication protocol (LM, NTLMv1, NTLMv2, Kerberos) is negotiated independently of the SMB version used.
The requester has never clearly shared the SMB and NTLM options they had configured.
These options and their impacts haven't really changed since Windows XP. What changes are the default values and, sometimes, the allowed values.
I thought that in workgroups we were sticking with LM/NTLM, and Kerberos in domains.
I know well that this exists in Samba, and Syno probably uses Samba, but NAS shouldn't get too carried away thinking they are DCs.
I hadn't touched NTLM, just SMB which I had restored and which is still set to SMB2 and 3. That said, the game is not completely won because after restarting the computer this morning, bam, no more mapping!
I then went back into secpol.msc to the version "send LM and NTLM-use NTLM2 session security if negotiated" which I had replaced with NTLM2 to the exclusion of NTLM and LM, then I restarted Windows: still no access through mapping after this restart.
In desperation, I reset the network settings and then it started working again; I was able to reconnect the folders of my NAS. I don't understand much about this instability. Nevertheless, it is indeed with the additional security layers induced by the two Windows 11 updates and SMB 7.2 update 1 that I am having issues.