Mount smb share from linux

: specifies the CIFS password. If this option is not given then the environment variable PASSWD is used. If the password is not specified directly or indirectly via an argument to mount mount.cifs will prompt for a password, unless the guest option is specified.

• uid= : sets the uid that will own all files on the mounted filesystem. It may be specified as either a username or a numeric uid. This parameter is ignored when the target server supports the CIFS Unix extensions (which samba does per default unless you disable it).
• gid= : sets the gid that will own all files on the mounted filesystem. It may be specified as either a groupname or a numeric gid. This parameter is ignored when the target server supports the CIFS Unix extensions.
• domain= : sets the domain (workgroup) of the user
• ip= : sets the destination host or IP address.
• guest: mount the share as guest and don’t prompt for a password.

There are other options but they are not that important to be usefull beside performance and really specific things.

NetBios name resolution with WINS

All networking programs at some point need to resolve a host name to an IP-Address. Usually this is done with a call to the function gethostbyname. This call is a library function and thus is handled in user space. Glibc systems such as Linux have the feature of using more than one lookup method to fulfill such a query. This is known as nsswitch (Name Service Switch). The config file is usually found in /etc/nsswitch.conf.

If a program wants to resolve the ip address of a host named ‘wiki’ it simply calls the function gethostbyname. The lookups done are the responsibility of the underlying glibc then. Glibc reads the /etc/nsswitch.conf and loads the library mentioned in the hosts line. Thats the key point: if there is a wins entry, glibc loads the libnss_wins.so which enables the NetBios Name Lookup. You got it then, you can resolve a Windows Name to an ip address.

So its simple: install the libnss_wins.so, add to your /etc/nsswitch.conf at line hosts the wins entry and the windows name resolution works. Your network setup should be ok for this, but thats not a matter of samba.

Step by Step list to get it working

Lets assume you have one of those ARM powered NAS boxes such as Buffalo et al make under your TV set and you want to access it from a desktop Linux box somewhere in your house.
You will need the IP address of said box! Often you can find this out via the web interface of your router.

As root edit /etc/fstab using your favourite editor
e.g. sudo gedit /etc/fstab
At the end of the file add a line that looks like this:-

If you never set any users up on the NAS then it would look like this

Here is what one of my entries looks like

Now when I browse over to /mnt/oneterra I see all my files on my 1TB NAS! If I had left out the uid=myloginname I would only have read-only access, the _netdev is to tell Linux to wait for the network to be up before attempting the mount

For more try this link [1]

TODO: make a step by step list to solve most of the problems

Here’s the verbatim commands I used (SuSE 10.0 to Buffalo Link Station). Notice I knew the IP address, in my case the SMB name didn’t work and I didn’t bother making the Network Name «NetBios Name» Work as suggested above.

Mounting shares at logon time

If you want to automatically mount shares at user logon time the only way I found is doing it with the pam_mount module. It is the only way to do an authenticated mount without requiring the user to store the password in a file or entering it on a terminal.

Источник

Mount SMB Azure file share on Linux

Azure Files is Microsoft’s easy to use cloud file system. Azure file shares can be mounted in Linux distributions using the SMB kernel client.

The recommended way to mount an Azure file share on Linux is using SMB 3.1.1. By default, Azure Files requires encryption in transit, which is supported by SMB 3.0+. Azure Files also supports SMB 2.1, which doesn’t support encryption in transit, but you may not mount Azure file shares with SMB 2.1 from another Azure region or on-premises for security reasons. Unless your application specifically requires SMB 2.1, use SMB 3.1.1.

If your Linux distribution isn’t listed in the above table, you can check the Linux kernel version with the uname command:

SMB 2.1 support was added to Linux kernel version 3.7. If you are using a version of the Linux kernel after 3.7, it should support SMB 2.1.

Applies to

Prerequisites

Ensure the cifs-utils package is installed.
The cifs-utils package can be installed using the package manager on the Linux distribution of your choice.

On Ubuntu and Debian, use the apt package manager:

On Red Hat Enterprise Linux 8+ use the dnf package manager:

On older versions of Red Hat Enterprise Linux use the yum package manager:

On SUSE Linux Enterprise Server, use the zypper package manager:

On other distributions, use the appropriate package manager or compile from source.

The most recent version of the Azure Command Line Interface (CLI). For more information on how to install the Azure CLI, see Install the Azure CLI and select your operating system. If you prefer to use the Azure PowerShell module in PowerShell 6+, you may, however the instructions in this article are for the Azure CLI.

Ensure port 445 is open: SMB communicates over TCP port 445 — check to see if your firewall is not blocking TCP ports 445 from client machine. Replace and then run the following script:

If the connection was successful, you should see something similar to the following output:

If you are unable to open up port 445 on your corporate network or are blocked from doing so by an ISP, you may use a VPN connection or ExpressRoute to work around port 445. For more information, see Networking considerations for direct Azure file share access.

Mount the Azure file share on-demand with mount

When you mount a file share on a Linux OS, your remote file share is represented as a folder in your local file system. You can mount file shares to anywhere on your system. The following example mounts under the /mount path. You can change this to your preferred path you want by modifying the $mntRoot variable.

Replace , , and with the appropriate information for your environment:

Next, mount the file share using the mount command. In the following example, the $smbPath command is populated using the fully qualified domain name for the storage account’s file endpoint and $storageAccountKey is populated with the storage account key.

Starting in Linux kernel version 5.0, SMB 3.1.1 is the default negotiated protocol. If you’re using a version of the Linux kernel older than 5.0, specify vers=3.1.1 in the mount options list.

You can use uid / gid or dir_mode and file_mode in the mount options for the mount command to set permissions. For more information on how to set permissions, see UNIX numeric notation on Wikipedia.

You can also mount the same Azure file share to multiple mount points if desired. When you are done using the Azure file share, use sudo umount $mntPath to unmount the share.

Automatically mount file shares

When you mount a file share on a Linux OS, your remote file share is represented as a folder in your local file system. You can mount file shares to anywhere on your system. The following example mounts under the /mount path. You can change this to your preferred path you want by modifying the $mntRoot variable.

To mount an Azure file share on Linux, use the storage account name as the username of the file share, and the storage account key as the password. Since the storage account credentials may change over time, you should store the credentials for the storage account separately from the mount configuration.

The following example shows how to create a file to store the credentials. Remember to replace and with the appropriate information for your environment.

To automatically mount a file share, you have a choice between using a static mount via the /etc/fstab utility or using a dynamic mount via the autofs utility.

Static mount with /etc/fstab

Using the earlier environment, create a folder for your storage account/file share under your mount folder. Replace with the appropriate name of your Azure file share.

Finally, create a record in the /etc/fstab file for your Azure file share. In the command below, the default 0755 Linux file and folder permissions are used, which means read, write, and execute for the owner (based on the file/directory Linux owner), read and execute for users in owner group, and read and execute for others on the system. You may wish to set alternate uid and gid or dir_mode and file_mode permissions on mount as desired. For more information on how to set permissions, see UNIX numeric notation on Wikipedia.

Starting in Linux kernel version 5.0, SMB 3.1.1 is the default negotiated protocol. You can specify alternate protocol versions using the vers mount option (protocol versions are 3.1.1 , 3.0 , and 2.1 ).

Dynamically mount with autofs

To dynamically mount a file share with the autofs utility, install it using the package manager on the Linux distribution of your choice.

On Ubuntu and Debian distributions, use the apt package manager:

On Red Hat Enterprise Linux 8+, use the dnf package manager:

On older versions of Red Hat Enterprise Linux, use the yum package manager:

On SUSE Linux Enterprise Server, use the zypper package manager:

Next, update the autofs configuration files.

The final step is to restart the autofs service.

Next steps

See these links for more information about Azure Files:

Источник