NAS folders mounted as SMB_1 on client

[kilbey1]

When I run command "smbutil statshares -a" it shows SMB_1 for my mounts.

Code: Select all

==================================================================================================
SHARE                         ATTRIBUTE TYPE                VALUE
==================================================================================================
Music                         
                              SERVER_NAME                   192.168.0.61
                              USER_ID                       501
                              SMB_NEGOTIATE                 SMBV_NEG_SMB1_ENABLED
                              SMB_VERSION                   SMB_1
                              SMB_SHARE_TYPE                UNKNOWN
                              EXTENDED_SECURITY_SUPPORTED   TRUE
                              LARGE_FILE_SUPPORTED          TRUE

--------------------------------------------------------------------------------------------------
usbshare1                     
                              SERVER_NAME                   192.168.0.61
                              USER_ID                       501
                              SMB_NEGOTIATE                 SMBV_NEG_SMB1_ENABLED
                              SMB_VERSION                   SMB_1
                              SMB_SHARE_TYPE                UNKNOWN
                              EXTENDED_SECURITY_SUPPORTED   TRUE
                              LARGE_FILE_SUPPORTED          TRUE

--------------------------------------------------------------------------------------------------

Should these mount as NT1 or SMB3 (or later), and if so, is it recommended to edit the samba config file on the NAS?

It would be great if the TOS user interface gave the option for minimum client mount.

[matt_30]

I have the same problem.

You are opening up a real can of worms when talking to TerraMaster about SNB support.

This was originally raised here viewtopic.php?f=23&t=1557&start=10 howerver TerraMaster refuse to understand the problem.

They have a very basic implementation of the mount command

You can not:

• mount using fstab
• Mount using the gui
• Mount using any extended parameters in the mount man page (https://linux.die.net/man/8/mount)
• access mounts in the gui[
• access any mounts on any account apart from root

Most of this could be fixed but adding the cifs-utils package to the next release however teamster refuse to listen to this I spent hours over muliple support sessions being given pdf's on how to access cifs mounts on a windows box by customer support agents who refused to understand the problem here or even read the case notes admitting that they did not understand the Linux command line while reassuring me there was not a problem with the command.

I tested my commands on Raspberry Pi's to prove where the problem was and that the configurations on my other devices were not the fault and they did not understand this concept.

finally, we were able to get snbv1 mounts working by logging into the command line as root and running the command:

mount -t cifs -o username=,password=,vers=1.0 //192.168.0.162/Public /mnt/folder/folder/

The biggest hurdle was the position of the -o flag. The command must be formatted in that exact structure. On other linux devices they are a bit more forgiving with how you structure the command due to the cifs-utils package. Without the Cifs-utils package and more specifically the mount.cifs file in the /bin folder you get very limited support for smb in general. I have been told in a support session that they will look at getting the cifs-utils package added but i very much doubt the engineer i was talking to formally raised this as a program to add into the next build.

That command should work for you if you change the IP's and folder names to where you want to go you can then use the cp command on the command line in a root session to move your files. The above command also assumes you have no username or password on the share.


This is a very frustrating problem I got a very frustrating attitude to in my support requests where there is such a simple fix.

Please let me know how you get on with this.

Matt.