DS1821+ Issue sharing folder

[Gibsonm]

Good morning,

I've just purchased a DS1821+ with 4x 8TB drives, running DSM 7.1.

Using NASCompares "Synology NAS Setup Guide Part I - 2021/2022 - DSM 7 - RAID - VOLUMES - SHARES - MAPPED DRIVES"

I've created a SHR pool and a volume.

I think I've shared it correctly and have setup relevant users, etc.

My issue is when I come to map it, the Synology Assistant doesn't allow me to log in.

Right clicking on the NAS and selecting "Map Drive" results in:

From the video, I had expected to be asked to provide a UserID and password. Hitting "next" results in:

There is no data on the drive so if I need to "Factory Reset" or similar, happy to.

 

[EAZ1964]

There is a setting in the smb section of the nas, that allows the unsafe ntlmv1, you can try that one and see if it works to map, just for diagnose.
if it works, make the required change in Windows. The ntlmv2 is security improvement that should be in place, so revert the setting on v2 in the NAS anyway.
it appears that in many cases Windows machines were not updated on this setting.

I lost access to shared folders via SMB after updating to DSM 7. What can I do? - Synology Knowledge Center

Synology Knowledge Center provides you with answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.

kb.synology.com

 

[Gibsonm]

Update:

I got frustrated and opted to uninstall and re-install the Synology Assistant.

Same version as before 7.0.3-50049, but now it works!

 

[Gerard]

Update:

I got frustrated and opted to uninstall and re-install the Synology Assistant.

Same version as before 7.0.3-50049, but now it works!


View attachment 10197

Its mapping by IP address there, which was already confirmed that worked before; just in a different way. You should also try mapping by the host name and see if you’re still getting a failure to ensure that everything is working as it should. Otherwise it’s working half assed in my opinion.

 

[Gibsonm]

Its mapping by IP address there, which was already confirmed that worked before; just in a different way. You should also try mapping by the host name and see if you’re still getting a failure to ensure that everything is working as it should. Otherwise it’s working half assed in my opinion.

The "problem" was as outlined in the first post - I couldn't use login and connect.

I now can.

Hence I ticked "solution".

 

[Coop777]

Glad to hear. The 1821+ is a fine NAS model and should serve you well. Depending on what you may do with it I would recommend adding RAM to it.

 

[Gibsonm]

Its mapping by IP address there, which was already confirmed that worked before; just in a different way. You should also try mapping by the host name and see if you’re still getting a failure to ensure that everything is working as it should. Otherwise it’s working half assed in my opinion.

More randomness.

A friend told me that Synology doesn't like underscores "_" in names. accordingly, I changed "Gibson_DS1821" to "Gibson-DS1821".

As a result Synology Drive Client would now connect to the NAS.

Unfortunately Windows drive mapping now failed using IP addresses.

However using "\\Gibson-DS1821" gave me:

And I now happily have shares, not based on IP addresses:

Presumably if the NAS changes its IP address in the future these will still resolve!

Now onto Network Failover - another as far as I can make out "hidden feature". New post to follow.

-- post merged: 18. Jul 2022 --

Glad to hear. The 1821+ is a fine NAS model and should serve you well. Depending on what you may do with it I would recommend adding RAM to it.

Yes ECC RAM was on the shopping list for "Prime Day" but as covered elsewhere the "deals" in Australia were atrocious.

I also have a spare Samsung 1TB SSD that I thought might be useful as a cache.

 

[Gerard]

And I now happily have shares, not based on IP addresses:

awesome news!