Hello,

I'm new on this forum and this is my first question. I have spent multiple days to find the solution to mount an old network disk (supports only SMB1) in Openmediavault 5 with a plug in called: Remote Mount.

It doens't matter which options/settings I edit, nothing works. I already edit the smb.conf to accepet SMB1 (NT1) connections, I already used the option vers=1.0 with sec=none / sec=ntlm and so on. Even putting more lines in the smb.conf, like: "guest only = yes", "guest ok = yes" and so on. Everything what I could fine on google, I tried it!

The network disk does not have any security for the shared folders, there are no usernames and no password. When I enable SMB1 on a Windows client, then I can acces the shares on the network disk right away.

With smbclient I can list the shares without any problems: "smbclient -L //192.168.0.3/ -N", see below:

Sharename Type Comment
--------- ---- -------
NAS-BACKUP Disk
Backup Disk
IPC$ IPC
Reconnecting with SMB1 for workgroup listing.

Server Comment
--------- -------

Workgroup Master
--------- -------


The trouble starts when I try to mount the disk, even without the Openmediavault Remote mount plugin.

I know that SMB1 protocol is a security risk and so on but I have spent to much time that I must make it work (it is only for personal/private use).

So... if there is someone who can help me with this and have some golden tips, please let me know!

Thank you

Can you provide specific information about this "old network disk"
Which share are you trying to mount?

From the command line try:
/mnt/some_where is just an example but the directory needs to exist and by convention is under /mnt or /media.

Hello Michael,

Thanks for your reply!

The old disk is an FREECOM 1TB Network Drive / LAN & USB 2.0 model: SWYBAH (picture: https://images-eu.ssl-images-amazon....X300_QL70_.jpg)
On the web interface from that disk, I can create multiple shares. One of them is: "NAS-BACKUP". But all the shares on de disk are the same, there are no differences (except the share names of course).

Here is the output of the command:

root@NAS-OTHMAN:~# mount -t cifs -o guest,sec=ntlm,vers=1.0 //192.168.0.3/NAS-Backup /mnt/share/
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
root@NAS-OTHMAN:~#

Changing options to sec=none might work.

I've already tried , se my first post: "I already used the option vers=1.0 with sec=none / sec=ntlm and so on."

root@NAS-OTHMAN:~# mount -t cifs -o guest,sec=ntlm,vers=1.0 //192.168.0.3/NAS-Backup /mnt/share/
root@NAS-OTHMAN:~# mount -t cifs -o guest,sec=none,vers=1.0 //192.168.0.3/nas-backup /mnt/share/
root@NAS-OTHMAN:~# mount -t cifs -o sec=none,vers=1.0 //192.168.0.3/nas-backup /mnt/share/

All these commands gives the same output:
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

root@NAS-OTHMAN:~# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=1 ttl=32 time=0.229 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=32 time=0.161 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=32 time=0.212 ms

root@NAS-OTHMAN:~# smbclient -L 192.168.0.3
Enter WORKGROUP\root's password:{Here I just hit Enter. without entering a password}
Sharename Type Comment
--------- ---- -------
NAS-BACKUP Disk
IPC$ IPC
Reconnecting with SMB1 for workgroup listing.

Server Comment
--------- -------

Workgroup Master
--------- -------

root@NAS-OTHMAN:~# sudo nano /etc/samba/smb.conf -- (I tried with different config settings, below is how it is now):
[global]

workgroup = WORKGROUP
client ipc signing = auto
client max protocol = NT1
guest only = yes
guest ok = yes
guest account = nobody
public = yes

------
Everithing what comes below in the config file, is default.

it's so frustrated!

The smb.conf file basically only configures the server running on your Open Media Vault box and not the mount command trying to access another server.

Another option to try is nounix

Adding --verbose might provide more information.

Ah, good to know. Thank you!

OMG! "nounix" did the job!! thank you very much !
From here I can finally move on, thanks to you!

Hero

Please mark it as solved then.

Done.