Recently upgraded to DSM 7.0 and lost access via SMB.

[Stathis Alexopoulos]

Recently upgraded to DSM 7.0 and lost access via SMB.

Here the steps that i followed.
1. Backup everything via HyperBackup
2. Upgrade to DSM 7
2. Restore everything

After that, all of the users and shared folders were restored perfectly, but allthough users have access to DiskStation through WEB they cannot login through SMB.
File explorer responds to login with "\\nas is not accessible.You might not having permission to use this network resourse. Contact..."

I tried it with a few different users including a user belonging to administrators group.

In Windows site i tried the following.
1. On "Windows Credential Manager" delete the entry for nas and tried again.
2. Reboot Windows machine and tried again.

Every time, windows respond is not accessible

Any idea will be appreciated.

Stathis Alexopoulos

 

[Telos]

Maybe this will help.

TLDR:

 

[Stathis Alexopoulos]

There was no difference between two files, except the workgroup name and min protocol which was 1 in my case because i have a mix of Windows 10 and Windows XP in my network.

Anyway I did the mentioned solution but did not worked, either with min protocol 1 or 2.

Is there any other place to look at?

 

[fredbert]

I’m having a problem with DSM 7 local users and LDAP users with the same name (I.e. exc. LDAP domain). Affects access to shared folders and SMB. If one account is assigned no access but the other has read-only/read-write then both get the lower access rights.

Still working this out with Synology Support.

 

[Stathis Alexopoulos]

Finally solved the problem. Here the description of steps for the future reader.

First of all, DSM 7 has a new application on user properties called SMB. So for having access must enable it for every user or group.

Having done that, most of the machines connected perfectly.

But there were some machines who refused to login successfully. The login failed and on Log Center of DSM there was an entry "User [xxxxxx] from [xx.xx.xx.xx] failed to log in via [SMB] due to [NTLMv1 not permitted]."

To solve it, i followed the suggestion of @bazzer at community.synology.com

You need administration rights on your Windows machine to do it.

1. Hit Windows key + S to open the Search on taskbar
2. Type Security and select the "Local Security Policy"
3. In the left pane expand Local Policies and select Security Options
4. In the right pane select "Network Security: LAN Manager Authentication Level" and double-click it.
5. Under the Local Security Tab change the drop down box from "Send LM & NTLM responses" to "Send NTLMv2 responses only."

After that, the problem solved.

 

[EAZ1964]

Good catch! Succes and thanks for sharing.

 

[tomassek]

Finally solved the problem. Here the description of steps for the future reader.

First of all, DSM 7 has a new application on user properties called SMB. So for having access must enable it for every user or group.

Having done that, most of the machines connected perfectly.

But there were some machines who refused to login successfully. The login failed and on Log Center of DSM there was an entry "User [xxxxxx] from [xx.xx.xx.xx] failed to log in via [SMB] due to [NTLMv1 not permitted]."

To solve it, i followed the suggestion of @bazzer at community.synology.com

You need administration rights on your Windows machine to do it.

1. Hit Windows key + S to open the Search on taskbar
2. Type Security and select the "Local Security Policy"
3. In the left pane expand Local Policies and select Security Options
4. In the right pane select "Network Security: LAN Manager Authentication Level" and double-click it.
5. Under the Local Security Tab change the drop down box from "Send LM & NTLM responses" to "Send NTLMv2 responses only."

After that, the problem solved.

It's don't work in my Synology. We Solved this:

Copy
/etc.defaults/samba/smb.conf
to
/etc/samba/smb.conf via SSH (putty, midnight commander or something)
clear the SMB cache
and all works fine in the moment

Regards

 

[RayC]

Ran into this problem with a new DS920+ running DSM 7.0.1-42218 Update 3.
We have about 15 Synology NAS units of various vintages and some aging NAS of other brands that require SMB1.
No amount of specifying username/password combinations allowed us to access the Shared Folder using SMB.
Thought it was an SMB1 problem until I read the log message closely: "User [administrator] from <IP address> failed to log in via [SMB] due to [NTLMv1 not permitted].
The full solution is described by Stahis above, but there is a new option in Control Panel:
File Services > SMB > Advanced Settings > Other > "Enable NTLMv1 authentication"
This allows login until you can get NTLMv2 fully operational.
Ray

 

[MediaManny]

@tomassek -- I signed-up just to thank you for your post.

I spent hours with this Synology DSM 7 upgrade breaks SMB issue, nothing worked.

It wasn't until I replaced the smb.conf file, that I fixed the problem -- thanks to your post!

sudo su
rm /etc/samba/smb.conf
cp /etc/samba.defaults/smb.conf /etc/samba/smb.conf

 

[morettomail]

Dears and dear @MediaManny
I have the same problem but I can't solve as you said: it seems the my file sys is different.
I logged in ssh of diskstation but when I apply the commands it seems that the folders does not exist. I'm not at all a Linux expert, could you kindly advice?
below some trials

root@Diskstation:~# sudo -i cd etc
-ash: line 0: cd: etc: No such file or directory
root@Diskstation:~# sudo mkdir -p /etc/samba
root@Diskstation:~# sudo cp /usr/share/samba/smb.conf /etc/samba
cp: cannot stat '/usr/share/samba/smb.conf': No such file or directory
root@Diskstation:~# sudo su
rm /etc/samba/smb.conf
cp /etc/samba.defaults/smb.conf /etc/samba/smb.confash-4.4# rm /etc/samba/smb.conf
rm: cannot remove '/etc/samba/smb.conf': No such file or directory
ash-4.4# cp /etc/samba.defaults/smb.conf /etc/samba/smb.conf
cp: cannot stat '/etc/samba.defaults/smb.conf': No such file or directory
ash-4.4# ok
ash: ok: command not found
ash-4.4# sudo mkdir -p /etc/samba
ash-4.4# cd..
ash: cd..: command not found
ash-4.4# cp /etc/samba.defaults/smb.conf /etc/samba/smb.confash-4.4# rm /etc/samba/smb.conf
cp: target '/etc/samba/smb.conf' is not a directory
ash-4.4# sudo cp /etc/samba.defaults/smb.conf /etc/samba/smb.confash-4.4# rm /etc/samba/smb.conf
cp: target '/etc/samba/smb.conf' is not a directory
ash-4.4# cp /etc/samba.defaults/ /etc/samba/smb.confash-4.4# rm /etc/samba/smb.conf
cp: target '/etc/samba/smb.conf' is not a directory
ash-4.4# cp /etc/samba.defaults/smb.conf /etc/samba/smb.conf
cp: cannot stat '/etc/samba.defaults/smb.conf': No such file or directory
ash-4.4# cp /etc/samba.defaults/smb.conf /etc/samba
cp: cannot stat '/etc/samba.defaults/smb.conf': No such file or directory
ash-4.4#

 

[Deleted member 5784]

cp /etc/samba.defaults/smb.conf /etc/samba/smb.confash-4.4# rm /etc/samba/smb.conf

These lines where you try and copy a file all contain the junk in bold at the end. It's not possible to tell if this is just bad formatting in your post or if you are actually typing this in your copy command.

To be clear, the commands you need to type are:

sudo su <RETURN>
rm /etc/samba/smb.conf <RETURN>
cp /etc/samba.defaults/smb.conf /etc/samba/smb.conf <RETURN>
exit <RETURN>

The <RETURN> part means 'Press the Return button'; don't type this.

Then, clear your SMB cache in the Synology GUI as per @Telos post above.

 

[morettomail]

Sooooo kind! This night I will try again.
what it is sure is that where I command rm /etc/samba/smb.conf, the prompt replies that there is no file at that path

 

[Deleted member 5784]

Sooooo kind! This night I will try again.
what it is sure is that where I command rm /etc/samba/smb.conf, the prompt replies that there is no file at that path

That's fine; this just means you have already deleted it. We're just making sure it's deleted before you try to recreate it with the next command.

 

[morettomail]

Thanks @Fortran
I hate to mind you but I have just tryed with no luck

If i do "suso su" on ldibiase@diskstation the password is prompt but it doesn't recognize my password and give just "ash-4.4#"
no idea....I'm really ignorant about linux

 

[Telos]

It didn't ignore it. You now have root prompt.

 

[Deleted member 5784]

It didn't ignore it. You now have root prompt.

@Telos - I'm not in front of a Syno at the moment...do you know where the default smb.conf is on the new DSM 7?? @morettomail cant seem to find it.

If you could take a look and give him the correct cp.... command that'd be a .

Cheers!

-- post merged: 27. Feb 2023 --

Ok I'm on a Syno. It lools like the location of the default smb.conf has changed since the instructions at the top of this post were posted in 2021.

@morettomail the correct cp command is below:

cp /etc.defaults/samba/smb.conf /etc/samba/smb.conf

Follow the steps in post 11, but substitute the above line for the previous 'cp' line.

 

[Telos]

@Telos - I'm not in front of a Syno at the moment

Sorry... me neither. Looks like you got there before me.

 

[morettomail]

It seems taken now! I have to see if this solve the issue in my music streamer, now.
Meanwhile i do not know how to thank you for kindness!!!