Troubleshooting Synology Mapping on Windows: Resolving the “username/password are incorrect ” Error – message

Set server name as “Syn1”. Using User1, Password1.  In administrators group, so already has full access rights, full read/write permissions, and the only enabled user account on the NAS to date.

On PC1, all drives, files, NAS control etc etc are enabled and everything works entirely as expected.

I then move to PC2.

Web access via chrome (User1 Password1) gives complete access to the NAS DSM desktop, settings etc, exactly the same as on PC1

In both Network and Explorer, “Syn1” clearly shows as a network device, so discovery etc working.

But, click on “Syn1” in either Network or Win Explorer, pauses briefly, then requests username & password.  Enter User1, Password1 … and I get told they’re wrong.  Syn2 shown in the pic above works fine – it’s a DS420j, set to be replaced by this new DS923+

Same user and password on the same PC allows me to change any NAS settings in a browser !! but doesn’t allow access by any other method.  Turning off Virus scanner makes no difference.

Creating a mapped drive or desktop shortcut … I cut & pasted the password … still get:

This is misleading, as the password is correct. (I blanked the actual username with XXX’s.)

Stumped, doesn’t cover it ☹

From PC2, via browser, I created a new user2, with admin rights.  I can’t access that either, except via browser.  From Explorer etc I get the same ‘the specified network password is not correct’

If you can figure this out, I will most certainly treat you to a coffee! (FYI I already subscribed to your YouTube vids.)

Additional info:  Currently just a single user created on NAS. Both PC’s Win10Pro x64 up to date. Both ‘beasts’ with masses of RAM and tens of TB storage.  On same network, with same “WORKGROUP” name.

I believe I’ve cracked it!

When setting up the NAS, I declined the option for detailed logging.  However, I ventured into the ‘simple’ log on the NAS and selected ‘Connection’.

I found that the first PC was shown as connecting ” via [CIFS(SMB3)]accessed shared folder [V1]””

While PC2 was shown as failing trying to connect “failed to log in via [SMB] due to [NTLMv1 not permitted]”

Asking that nice Mr. Google, I found someone else had had similar problem, and solution was to enable NVLMv1 in the NAS.

However, if I go to this, DSM reads the riot act about it being insecure, and advising heavily against it.  So, I left it alone.

So instead, I tried the opposite approach, and disabled NTLMv1 in the PC’s Registry. Figured it worth a try …

Tried to log into a folder on the NAS, and voila!  Straight in!!

Heading back to the Synology log, the second PC is now using the same [CIFS(SMB3)] 🙂

It is as yet unclear as to what if any other problems may develop for other apps or processes due to this seemingly insignificant, minor change, but for now at least, I have full access to the NAS from all PC’S.

So should you encounter this strange issue again in future, you’ll know where to look. I understand it can occur moving from DSM 6 to 7 (my old NAS is still DSM6.4).  Old NAS is still accessible too, from all PC’s

Thanks muchly for trying to help.  I’ll head off to YouTube and donate your coffee.

Regards,

  Kevin

Where to Buy a Product
			VISIT RETAILER ➤
			VISIT RETAILER ➤
			VISIT RETAILER ➤
			VISIT RETAILER ➤

☕ WE LOVE COFFEE ☕

Or support us by using our affiliate links on Amazon UK and Amazon US