Can't mount a Windows share using the mount.cifs vers= option on SLES 11
This document (7018804) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)
SUSE Linux Enterprise Server 11 Service Pack 2 (SLES 11 SP2)
SUSE Linux Enterprise Server 11 Service Pack 1 (SLES 11 SP1)
The Windows server has been configured to only allow SMBv2.
If the Windows server is configured to allow SMBv1 the mount command works regardless of the presence of the vers= option.
SLES12 would be an example of a version of the SLES OS that has a kernel version that is later than 3.5 which does have the vers= option.
The vers= option is available on SLES in kernels that are later than 3.5.
On SLES 11 the kernel's mount command doesn't actually error out on its own when this option is used but simply ignores the option and sends SMBv1 headers.
When the Windows server is configured to not allow SMBv1 the Windows server will send a TCP RST to the Negotiate Protocol Request sent from the SLES server with an SMBv1 header. This is to be expected.
This TCP RST results in an error like this being seen at the console:
mount error (112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7018804
- Creation Date: 12-Apr-2017
- Modified Date:03-Mar-2020
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com