Linux Force Default Mount CIFS Version to 3.0
up vote
2
down vote
favorite
I'm running Ubuntu Server 16.04.3 LTS 64-Bit with cifs-utils installed, as a VM, on a VMWare ESXi 6.5 hyper-visor.
I have a regular network share setup on Windows Server 2016.
The objective is to utilize Veeam Linux Agent to Backup this Linux VM to a Windows Share via CIFS.
The Problem:
When I am configuring Veeam to use CIFS, (viewing the logs) veeam is executing this command to connect to the network share:
mount -t cifs -o username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It gives me the error:
mount error(112): Host is down.
When I run the command manually, it does the same thing.
However when I run the command like this:
mount -t cifs -o vers=3.0,username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It mounts without issue same if I use 2.0 as well.
The problem is, there is no way to force version 3.0 in Veeam.
So, I need to be able to force this in Linux some how.
I've seen others have ran into this issue as well, but no solution was presented.
I've attempted the following (based on what I found):
Added the following lines to /etc/samba/smb.conf
server min protocol = SMB2
server max protocol = SMB3
client min protocol = SMB2
client max protocol = SMB3
min protocol = SMB2
max protocol = SMB3
client ipc min protocol = SMB2
I mixed and matched variations with reboots, to no avail.
linux ubuntu mount cifs smb3
asked Feb 23 at 17:32
Steven4x4
1113
add a comment |
up vote
2
down vote
favorite
I'm running Ubuntu Server 16.04.3 LTS 64-Bit with cifs-utils installed, as a VM, on a VMWare ESXi 6.5 hyper-visor.
I have a regular network share setup on Windows Server 2016.
The objective is to utilize Veeam Linux Agent to Backup this Linux VM to a Windows Share via CIFS.
The Problem:
When I am configuring Veeam to use CIFS, (viewing the logs) veeam is executing this command to connect to the network share:
mount -t cifs -o username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It gives me the error:
mount error(112): Host is down.
When I run the command manually, it does the same thing.
However when I run the command like this:
mount -t cifs -o vers=3.0,username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It mounts without issue same if I use 2.0 as well.
The problem is, there is no way to force version 3.0 in Veeam.
So, I need to be able to force this in Linux some how.
I've seen others have ran into this issue as well, but no solution was presented.
I've attempted the following (based on what I found):
Added the following lines to /etc/samba/smb.conf
server min protocol = SMB2
server max protocol = SMB3
client min protocol = SMB2
client max protocol = SMB3
min protocol = SMB2
max protocol = SMB3
client ipc min protocol = SMB2
I mixed and matched variations with reboots, to no avail.
linux ubuntu mount cifs smb3
asked Feb 23 at 17:32
Steven4x4
1113
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm running Ubuntu Server 16.04.3 LTS 64-Bit with cifs-utils installed, as a VM, on a VMWare ESXi 6.5 hyper-visor.
I have a regular network share setup on Windows Server 2016.
The objective is to utilize Veeam Linux Agent to Backup this Linux VM to a Windows Share via CIFS.
The Problem:
When I am configuring Veeam to use CIFS, (viewing the logs) veeam is executing this command to connect to the network share:
mount -t cifs -o username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It gives me the error:
mount error(112): Host is down.
When I run the command manually, it does the same thing.
However when I run the command like this:
mount -t cifs -o vers=3.0,username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It mounts without issue same if I use 2.0 as well.
The problem is, there is no way to force version 3.0 in Veeam.
So, I need to be able to force this in Linux some how.
I've seen others have ran into this issue as well, but no solution was presented.
I've attempted the following (based on what I found):
Added the following lines to /etc/samba/smb.conf
server min protocol = SMB2
server max protocol = SMB3
client min protocol = SMB2
client max protocol = SMB3
min protocol = SMB2
max protocol = SMB3
client ipc min protocol = SMB2
I mixed and matched variations with reboots, to no avail.
linux ubuntu mount cifs smb3
asked Feb 23 at 17:32
Steven4x4
1113
I'm running Ubuntu Server 16.04.3 LTS 64-Bit with cifs-utils installed, as a VM, on a VMWare ESXi 6.5 hyper-visor.
I have a regular network share setup on Windows Server 2016.
The objective is to utilize Veeam Linux Agent to Backup this Linux VM to a Windows Share via CIFS.
The Problem:
When I am configuring Veeam to use CIFS, (viewing the logs) veeam is executing this command to connect to the network share:
mount -t cifs -o username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It gives me the error:
mount error(112): Host is down.
When I run the command manually, it does the same thing.
However when I run the command like this:
mount -t cifs -o vers=3.0,username=MyUsername,password=*,rw,soft //MyServerIP/MyShare /tmp/veeam/MyServerIPMyShare
It mounts without issue same if I use 2.0 as well.
The problem is, there is no way to force version 3.0 in Veeam.
So, I need to be able to force this in Linux some how.
I've seen others have ran into this issue as well, but no solution was presented.
I've attempted the following (based on what I found):
Added the following lines to /etc/samba/smb.conf
server min protocol = SMB2
server max protocol = SMB3
client min protocol = SMB2
client max protocol = SMB3
min protocol = SMB2
max protocol = SMB3
client ipc min protocol = SMB2
I mixed and matched variations with reboots, to no avail.
linux ubuntu mount cifs smb3
linux ubuntu mount cifs smb3
asked Feb 23 at 17:32
Steven4x4
1113
asked Feb 23 at 17:32
Steven4x4
1113
edited Feb 23 at 17:37
asked Feb 23 at 17:32
Steven4x4
1113
asked Feb 23 at 17:32
Steven4x4
1113
asked Feb 23 at 17:32
Steven4x4
1113
1113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
For a given mount.cifs version, I don't know of a way other than adding vers=3.0 to the command line (or to /etc/fstab). The mount.cifs driver ignores smb.conf. Historically it seems mount.cifs could not auto-negotiate, and simply tried one protocol version - 1.0 until July 2017, and 3.0 after that. (July 2017 being the date of the code change to cifs 4.13, not that earlier versions looked at that date at runtime!) From September 2017 it looks like it can auto-negotiate, defaulting to 2.1 or later (whatever the highest is that the server can offer).
Thus if you can upgrade your version of cifs, you should be able to get a different resulting protocol version even without specifying one explicitly.
Here is the mapping of mount.cifs, smb.conf and Windows protocol versions:
vers=3.0 is SMB3 i.e. Windows 8, Windows Server 2012
vers=2.1 is SMB2_10 i.e. Windows 7, Windows Server 2008 R2
vers=2.0 is SMB2_02 i.e. Vista SP1, Windows Server 2008
vers=1.0 is NT1 i.e. Windows 95, NT 4.0
answered May 17 at 13:35
stevek_mcc
58348
1
Importantly, "upgrade your version of cifs" means installing a new kernel version with a new cifs.ko module – not the cifs-utils package or the mount.cifs tool. (Also don't forget vers=3.1 for Windows 10.)
– grawity
May 17 at 13:50
@grawity - Also importantly, you need the matching mount.cifs to go with your new kernel. Without it, you can't pass in some of the new options (or new values for existing options).
– Michael Kohne
Oct 22 at 17:58
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1297724%2flinux-force-default-mount-cifs-version-to-3-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
For a given mount.cifs version, I don't know of a way other than adding vers=3.0 to the command line (or to /etc/fstab). The mount.cifs driver ignores smb.conf. Historically it seems mount.cifs could not auto-negotiate, and simply tried one protocol version - 1.0 until July 2017, and 3.0 after that. (July 2017 being the date of the code change to cifs 4.13, not that earlier versions looked at that date at runtime!) From September 2017 it looks like it can auto-negotiate, defaulting to 2.1 or later (whatever the highest is that the server can offer).
Thus if you can upgrade your version of cifs, you should be able to get a different resulting protocol version even without specifying one explicitly.
Here is the mapping of mount.cifs, smb.conf and Windows protocol versions:
vers=3.0 is SMB3 i.e. Windows 8, Windows Server 2012
vers=2.1 is SMB2_10 i.e. Windows 7, Windows Server 2008 R2
vers=2.0 is SMB2_02 i.e. Vista SP1, Windows Server 2008
vers=1.0 is NT1 i.e. Windows 95, NT 4.0
answered May 17 at 13:35
stevek_mcc
58348
1
Importantly, "upgrade your version of cifs" means installing a new kernel version with a new cifs.ko module – not the cifs-utils package or the mount.cifs tool. (Also don't forget vers=3.1 for Windows 10.)
– grawity
May 17 at 13:50
@grawity - Also importantly, you need the matching mount.cifs to go with your new kernel. Without it, you can't pass in some of the new options (or new values for existing options).
– Michael Kohne
Oct 22 at 17:58
add a comment |
up vote
0
down vote
For a given mount.cifs version, I don't know of a way other than adding vers=3.0 to the command line (or to /etc/fstab). The mount.cifs driver ignores smb.conf. Historically it seems mount.cifs could not auto-negotiate, and simply tried one protocol version - 1.0 until July 2017, and 3.0 after that. (July 2017 being the date of the code change to cifs 4.13, not that earlier versions looked at that date at runtime!) From September 2017 it looks like it can auto-negotiate, defaulting to 2.1 or later (whatever the highest is that the server can offer).
Thus if you can upgrade your version of cifs, you should be able to get a different resulting protocol version even without specifying one explicitly.
Here is the mapping of mount.cifs, smb.conf and Windows protocol versions:
vers=3.0 is SMB3 i.e. Windows 8, Windows Server 2012
vers=2.1 is SMB2_10 i.e. Windows 7, Windows Server 2008 R2
vers=2.0 is SMB2_02 i.e. Vista SP1, Windows Server 2008
vers=1.0 is NT1 i.e. Windows 95, NT 4.0
answered May 17 at 13:35
stevek_mcc
58348
1
Importantly, "upgrade your version of cifs" means installing a new kernel version with a new cifs.ko module – not the cifs-utils package or the mount.cifs tool. (Also don't forget vers=3.1 for Windows 10.)
– grawity
May 17 at 13:50
@grawity - Also importantly, you need the matching mount.cifs to go with your new kernel. Without it, you can't pass in some of the new options (or new values for existing options).
– Michael Kohne
Oct 22 at 17:58
add a comment |
up vote
0
down vote
up vote
0
down vote
For a given mount.cifs version, I don't know of a way other than adding vers=3.0 to the command line (or to /etc/fstab). The mount.cifs driver ignores smb.conf. Historically it seems mount.cifs could not auto-negotiate, and simply tried one protocol version - 1.0 until July 2017, and 3.0 after that. (July 2017 being the date of the code change to cifs 4.13, not that earlier versions looked at that date at runtime!) From September 2017 it looks like it can auto-negotiate, defaulting to 2.1 or later (whatever the highest is that the server can offer).
Thus if you can upgrade your version of cifs, you should be able to get a different resulting protocol version even without specifying one explicitly.
Here is the mapping of mount.cifs, smb.conf and Windows protocol versions:
vers=3.0 is SMB3 i.e. Windows 8, Windows Server 2012
vers=2.1 is SMB2_10 i.e. Windows 7, Windows Server 2008 R2
vers=2.0 is SMB2_02 i.e. Vista SP1, Windows Server 2008
vers=1.0 is NT1 i.e. Windows 95, NT 4.0
answered May 17 at 13:35
stevek_mcc
58348
For a given mount.cifs version, I don't know of a way other than adding vers=3.0 to the command line (or to /etc/fstab). The mount.cifs driver ignores smb.conf. Historically it seems mount.cifs could not auto-negotiate, and simply tried one protocol version - 1.0 until July 2017, and 3.0 after that. (July 2017 being the date of the code change to cifs 4.13, not that earlier versions looked at that date at runtime!) From September 2017 it looks like it can auto-negotiate, defaulting to 2.1 or later (whatever the highest is that the server can offer).
Thus if you can upgrade your version of cifs, you should be able to get a different resulting protocol version even without specifying one explicitly.
Here is the mapping of mount.cifs, smb.conf and Windows protocol versions:
vers=3.0 is SMB3 i.e. Windows 8, Windows Server 2012
vers=2.1 is SMB2_10 i.e. Windows 7, Windows Server 2008 R2
vers=2.0 is SMB2_02 i.e. Vista SP1, Windows Server 2008
vers=1.0 is NT1 i.e. Windows 95, NT 4.0
answered May 17 at 13:35
stevek_mcc
58348
answered May 17 at 13:35
stevek_mcc
58348
answered May 17 at 13:35
stevek_mcc
58348
answered May 17 at 13:35
stevek_mcc
58348
58348
1
Importantly, "upgrade your version of cifs" means installing a new kernel version with a new cifs.ko module – not the cifs-utils package or the mount.cifs tool. (Also don't forget vers=3.1 for Windows 10.)
– grawity
May 17 at 13:50
@grawity - Also importantly, you need the matching mount.cifs to go with your new kernel. Without it, you can't pass in some of the new options (or new values for existing options).
– Michael Kohne
Oct 22 at 17:58
add a comment |
1
Importantly, "upgrade your version of cifs" means installing a new kernel version with a new cifs.ko module – not the cifs-utils package or the mount.cifs tool. (Also don't forget vers=3.1 for Windows 10.)
– grawity
May 17 at 13:50
@grawity - Also importantly, you need the matching mount.cifs to go with your new kernel. Without it, you can't pass in some of the new options (or new values for existing options).
– Michael Kohne
Oct 22 at 17:58
1
1
Importantly, "upgrade your version of cifs" means installing a new kernel version with a new cifs.ko module – not the cifs-utils package or the mount.cifs tool. (Also don't forget vers=3.1 for Windows 10.)
– grawity
May 17 at 13:50
Importantly, "upgrade your version of cifs" means installing a new kernel version with a new cifs.ko module – not the cifs-utils package or the mount.cifs tool. (Also don't forget vers=3.1 for Windows 10.)
– grawity
May 17 at 13:50
@grawity - Also importantly, you need the matching mount.cifs to go with your new kernel. Without it, you can't pass in some of the new options (or new values for existing options).
– Michael Kohne
Oct 22 at 17:58
@grawity - Also importantly, you need the matching mount.cifs to go with your new kernel. Without it, you can't pass in some of the new options (or new values for existing options).
– Michael Kohne
Oct 22 at 17:58
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1297724%2flinux-force-default-mount-cifs-version-to-3-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
