Samba not working on OMV 4.x while working on OMV3.x

XabiX · Nov 20th 2017

Hello,

I am new and installed initially the OMV3 using the ISO (openmediavault_3.0.86-amd64) and got all my CAMs to work perfectly (at the 1st attempt). As I wanted to install zoneminder etc... I opted to install a Debian 9.2.1 with OMV4 which went all ok. I did the same GUI configuration (and double checked the smb.conf which look the same) but for some reasons my CAMs keep saying:
"Mounting to NAS server failed. Invalid directory or incorrect user name/password."

I tried to set log level to 3 but didn't see the logs popping up in /var/log/samba so not sure how to debut and move forward.

My CAMs are Hikvision and need to have a quota assigned to each directly. I emptyed the directories being shared by SMB to start clean.

Noted that quota seems wrong (see size of Corridor directory for ex)

Code

root@Debian:/srv/dev-disk-by-id-scsi-0QEMU_QEMU_HARDDISK_drive-scsi1-part1# ll
total 72
-rw-------  1 root       root      7168 nov.  19 14:18 aquota.group
-rw-------  1 root       root      7168 nov.  19 14:18 aquota.user
drwxrws---+ 2 Back       CAMs      4096 nov.  12 16:13 Back
drwxrws---+ 3 Corridor   CAMs      4096 nov.  12 16:14 Corridor
drwxr-xr-x  2 www-data   www-data  4096 nov.  19 15:19 events
drwxrwsr-x+ 2 Front      CAMs      4096 nov.  20 14:29 Front
drwxr-xr-x  2 www-data   www-data  4096 nov.  19 15:20 images
drwxrws---+ 2 Jossua     CAMs      4096 nov.  12 15:51 Jossua
drwxrws---+ 3 Livingroom CAMs      4096 nov.  12 19:04 Livingroom
drwx------  2 root       root     16384 fÃ©vr. 11  2017 lost+found
drwxrws---+ 3 Side       CAMs      4096 nov.  18 14:51 Side
drwxr-xr-x  2 www-data   www-data  4096 nov.  19 15:20 sounds
drwxrws---+ 2 Victorine  CAMs      4096 nov.  12 15:51 Victorine
root@Debian:/srv/dev-disk-by-id-scsi-0QEMU_QEMU_HARDDISK_drive-scsi1-part1# ll Corridor/
total 8
drwxrws---+ 2 Corridor CAMs 4096 nov.  12 16:14 datadir0
-rwxrwx---+ 1 Corridor CAMs   68 nov.  12 16:14 info.bin

Display More

Corridor shows a size not linked to the HD space and over the definedvalue.

Any idea of the issue? I don't necessary believe that my shares don't work because of this quota stuff but if you have some guidance on how to drill down the issue that would be appreciated.

I have posted most of the important screens but please ask if anything missing or strange.

Thanks
XabiX

Is there a way to export the OMV3 config and reimport in my Debian with OMV4? maybe that would do the trick quicker.

XabiX · Nov 20th 2017

Not sure why but the service is showing red and here are some outputs that may give a hint?

I did a start and it went back to my initial issue:

Code

root@Debian:~# systemctl start smbd
root@Debian:~# systemctl status smbd
â— smbd.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2017-11-20 21:44:16 CET; 4s ago
     Docs: man:smbd(8)
           man:samba(7)
           man:smb.conf(5)
 Main PID: 2482 (smbd)
   Status: "smbd: ready to serve connections..."
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/smbd.service
           â”œâ”€2482 /usr/sbin/smbd
           â”œâ”€2483 /usr/sbin/smbd
           â””â”€2484 /usr/sbin/smbd


nov. 20 21:44:15 Debian systemd[1]: Starting Samba SMB Daemon...
nov. 20 21:44:16 Debian systemd[1]: smbd.service: Supervising process 2482 which is not our child. We'll most likely not notice when it exits.
nov. 20 21:44:16 Debian systemd[1]: Started Samba SMB Daemon.

Display More

BTW I have succeed to connect from Windows on the shares but I am missing some parameters to ensure that one user can't access another one share.

At least the config seem exactly the same but this Hikvision cameras are touchy. I believe the issue is not on the OMV4 itself but I don't understant why it worked on OMV3. Trying to reset one camera to see.

Putting logs to Full i get:

Code

Nov 20 22:18:04 Debian smbd[10242]: [2017/11/20 22:18:04.902503,  1] ../source3/smbd/process.c:554(receive_smb_talloc)
Nov 20 22:18:04 Debian smbd[10242]:   receive_smb_raw_talloc failed for client ipv4:10.10.10.6:55283 read error = NT_STATUS_CONNECTION_RESET.
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.921957,  2] ../source3/smbd/sesssetup.c:563(setup_new_vc_session)
Nov 20 22:18:04 Debian smbd[10243]:   setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922135,  1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter)
Nov 20 22:18:04 Debian smbd[10243]:   WARNING: The "syslog" option is deprecated
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922153,  1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter)
Nov 20 22:18:04 Debian smbd[10243]:   WARNING: The "syslog only" option is deprecated
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922282,  1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter)
Nov 20 22:18:04 Debian smbd[10243]:   WARNING: The "null passwords" option is deprecated
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922309,  2] ../source3/param/loadparm.c:2685(lp_do_section)
Nov 20 22:18:04 Debian smbd[10243]:   Processing section "[Victorine]"
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922468,  2] ../source3/param/loadparm.c:2685(lp_do_section)
Nov 20 22:18:04 Debian smbd[10243]:   Processing section "[Side]"
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922702,  2] ../source3/param/loadparm.c:2685(lp_do_section)
Nov 20 22:18:04 Debian smbd[10243]:   Processing section "[LivingRoom]"
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922837,  2] ../source3/param/loadparm.c:2685(lp_do_section)
Nov 20 22:18:04 Debian smbd[10243]:   Processing section "[Jossua]"
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.922975,  2] ../source3/param/loadparm.c:2685(lp_do_section)
Nov 20 22:18:04 Debian smbd[10243]:   Processing section "[Front]"
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.923133,  2] ../source3/param/loadparm.c:2685(lp_do_section)
Nov 20 22:18:04 Debian smbd[10243]:   Processing section "[Corridor]"
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.923235,  2] ../source3/param/loadparm.c:2685(lp_do_section)
Nov 20 22:18:04 Debian smbd[10243]:   Processing section "[Back]"
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.923544,  2] ../libcli/auth/ntlm_check.c:424(ntlm_password_check)
Nov 20 22:18:04 Debian smbd[10243]:   ntlm_password_check: NTLMv1 passwords NOT PERMITTED for user Livingroom
Nov 20 22:18:04 Debian smbd[10243]: [2017/11/20 22:18:04.923638,  2] ../source3/auth/auth.c:315(auth_check_ntlm_password)
Nov 20 22:18:04 Debian smbd[10243]:   check_ntlm_password:  Authentication for user [Livingroom] -> [Livingroom] FAILED with error NT_STATUS_WRONG_PASSWORD
Nov 20 22:18:04 Debian smbd[10244]: [2017/11/20 22:18:04.934880,  2] ../source3/smbd/sesssetup.c:563(setup_new_vc_session)
Nov 20 22:18:04 Debian smbd[10244]:   setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
Nov 20 22:18:04 Debian smbd[10244]: [2017/11/20 22:18:04.935480,  1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter)

Display More

I have checked several times my pwd but they are the same. Could it be because in my pwd there is the character & ?

THANKS

XabiX · Nov 20th 2017

Interesting reading: Privileges and permissions explained under OMV

Not sure if the system permissions should still be root:user but then if that's the case then that may be my issue. When i created my share I did select "Recursive".

Is that then my issue? should i put them back on root:Front for example? or delete the shares and create them again maybe worth

Maybe the smb.conf file can be updated to avoid:
Nov 20 22:49:19 Debian smbd[20916]: WARNING: The "syslog" option is deprecated
Nov 20 22:49:19 Debian smbd[20916]: WARNING: The "syslog only" option is deprecated
Nov 20 22:49:19 Debian smbd[20916]: WARNING: The "null passwords" option is deprecated

Before the users had only one group and now in OMV4 there is this user group showing up. could this explain the differences? as my initial setup was exactly the same.

getting lost!

XabiX · Nov 28th 2017

Hello,

Just to update and close the thread. I have revert to OMV 3 and all works like a charm.
Not sure I need really OMV4 and I have limited knowledge to troubleshoot it

FYI: these are the settings that were needed for the Cameras in case someone was wondering what needed exactly to be done:
https://ipcamtalk.com/threads/…ameras.54/page-6#post-661

Happy OMV3 customer

gimble · Jan 14th 2018

Hello,

I had the same problem after a working OMV3 upgrade to OMV4 with Windows. I added following line to the [global] section in /etc/samba/smb.conf:

ntlm auth = yes

after a restart of the smbd everything was fine again.

Hope this helps

ttaeschn · Feb 5th 2018

Quote from gimble

Hello,

I had the same problem after a working OMV3 upgrade to OMV4 with Windows. I added following line to the [global] section in /etc/samba/smb.conf:

ntlm auth = yes

after a restart of the smbd everything was fine again.

Hope this helps

Display More

Worked for me. Many thanks!

cabrio_leo · Feb 5th 2018

Quote from gimble

I added following line to the [global] section in /etc/samba/smb.conf:

You shouldn´t edit /etc/samba/smb.conf directly. If you change SMB/CIFS settings in OMV the next time, the smb.conf is overwritten by OMV. You can force this by
CLI> omv-mkconf samba

Instead add your entry in the SMB/CIFS settings -> Advanced settings -> Extra options field.

A second possibility is the add the next line to /etc/default/openmediavault

OMV_SAMBA_NTLM_AUTH="YES"

Then do a
CLI> omv-mkconf samba
CLI> service smbd restart
You can check your SAMBA settings with
CLI> testparm

This is tested for OMV3. I hope it works also for OMV4.

PHil8811 · Mar 10th 2023

Hi i have the same prob with my camera on my fresh install of OMV 6, i remember in OMV 4 it worked with this parameter but i don't get it in OMV 6 or maybe i don't do it in the good way?
If someone could help me

macom · Mar 11th 2023

add

ntlm auth = yes

in the extra options field in the GUI of OMV. Save and Apply.

PHil8811 · Mar 13th 2023

Hi thx a lot, like this?
If yes the test from the camera get no success, any ideas?

Best regards

raulfg3 · Mar 13th 2023

do you restart SAMBA like described on post #5? RE: Samba not working on OMV 4.x while working on OMV3.x

macom · Mar 13th 2023

Quote from PHil8811

If yes the test from the camera get no success, any ideas?

Did you save and apply?

You can try to additionally add

client min protocol = SMB1

also not sure if it has to be in the global samba extra options or in the extra options of the share.

PHil8811 · Mar 13th 2023

Quote from raulfg3

do you restart SAMBA like described on post #5? RE: Samba not working on OMV 4.x while working on OMV3.x

Hi thx for answer, yes and tried to restart server too but no success

PHil8811 · Mar 14th 2023

Quote from macom

Did you save and apply?

You can try to additionally add
client min protocol = SMB1

also not sure if it has to be in the global samba extra options or in the extra options of the share.

Display More

Hi thx for answer, yes save and apply
I tried in global samba extra option "client min protocol = SMB1" but I got this answer:

In share extra option no error but it doesn't work

Maybe you have another tips?

Best regards

macom · Mar 14th 2023

Try

client min protocol = NT1

You can copy the complete error message using the bell icon in the top right corner of the GUI and paste it in a code boy </>

Samba not working on OMV 4.x while working on OMV3.x

Participate now!

Tags