OMV6 - can SMB1 be enabled

Try to specify support for the minimum protocol version (server min protocol=NT1) in the SMB settings. And restart samba

# service smbd restart

Watch out, in the future Samba will deprecate this version and eventually Debian will update as well.

If your client can't really support SMB1, in the future you can evaluate a docker container with an old version just for SMB1, which will have to run on a different port.

I recently changed from OMV4 to OMV6 when I saw that OMV5 was about to reach end-of-life. I had the same issue with being unable to connect from an XP 'live' CD running Acronis True Image when trying to image my XP machine. Adding the line: server min protocol=NT1 into the SMB/CIFS Extra Options allowed to connect again but, sadly, the peformance is abominable. Every other hardware/software component is exactly the same as it was with OMV4 but now it takes 8-12 times longer to save a partition than it did then. Using FTP also works but it splits archives into 2GB chunks leaving me with lots of separate files.

Are there any performance tweaks to make imaging work as well as it did before?

Thanks.

sorry，help me please。。i follow this way，but the problem still exists

Still can't find omv6’s smb，MY zidoo can't work。。

the extra option should be servet min protocol=NT1

hi,

not sure it is "servet'

with these parameters,

ntlm auth = yes
min protocol = NT1
client min protocol = NT1

it worked yesterday and before, on OMV6 6.0.30-1 (Shaitan). I decide to keep this version, without update this OMV system, because of that:

But today, on 3 another systems, which have been updated today with about 40 updates (with a lot of samba xxxx items), shares are not seen on 2 kind of players.

the different available updates :

samba-common 2:4.13.13+dfsg-1~deb11u4
samba-common-bin 2:4.13.13+dfsg-1~deb11u4
samba-libs 2:4.13.13+dfsg-1~deb11u4
samba-vfs-modules 2:4.13.13+dfsg-1~deb11u4

i don't know how to go back with previous versions of that, except reinstall OMV5 (very less issues, compare to omv6).

edit: i decide to go back to 5.6, and with all sets as usual, all my shares are now seens on different systems.

Zitat von jackqqyl

Still can't find omv6’s smb，MY zidoo can't work。。

- in kodi reset smb setings to default

- add new network location (or edit your previous suorce)

- in the server name: put the IP of smb host (not the host name)

- in the Shared folder: put the smb shared folder name.

its works with me using omv 6 and Kodi 19 installed on Mi box s (no need to add any extra option parameters in omv smb settings)

Zitat von DavidLowe

Thank you! That worked perfectly.

Same prpoblem was here.

Thank You

Zitat von Genna

hi,

not sure it is "servet'

with these parameters,

Code

ntlm auth = yes
min protocol = NT1
client min protocol = NT1

Hi. My WS2003 does not connect to OMV6 using net use command - error 71.

I tried the options from the post above. The network drive began to be connected, but now access is allowed to everyone from any machines without a password.