mount cifs problems on ubuntu 18.04
up vote
0
down vote
favorite
I have a two similar Ubuntu servers 18.04 (4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) and trying to mount windows files server share on it. On one server it's mounting without problem but on second one failing with invalid argument error:
mount error(22): Invalid argument Refer to the mount.cifs(8) manual
page (e.g. man mount.cifs)
Executing same command on both servers:
mount -t cifs -o username=username,domain=domain-name //path/to/share
/mount/path
Kernel log write such messages:
[Tue Dec 4 13:48:36 2018] No dialect specified on mount. Default has
changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from
CIFS (SMB1). To use the less secure SMB1 dialect to access old servers
which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [Tue
Dec 4 13:48:36 2018] CIFS VFS: cifs_mount failed w/return code = -22
mount fstab cifs
asked Dec 4 at 12:00
Edgars
1
add a comment |
up vote
0
down vote
favorite
I have a two similar Ubuntu servers 18.04 (4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) and trying to mount windows files server share on it. On one server it's mounting without problem but on second one failing with invalid argument error:
mount error(22): Invalid argument Refer to the mount.cifs(8) manual
page (e.g. man mount.cifs)
Executing same command on both servers:
mount -t cifs -o username=username,domain=domain-name //path/to/share
/mount/path
Kernel log write such messages:
[Tue Dec 4 13:48:36 2018] No dialect specified on mount. Default has
changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from
CIFS (SMB1). To use the less secure SMB1 dialect to access old servers
which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [Tue
Dec 4 13:48:36 2018] CIFS VFS: cifs_mount failed w/return code = -22
mount fstab cifs
asked Dec 4 at 12:00
Edgars
1
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a two similar Ubuntu servers 18.04 (4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) and trying to mount windows files server share on it. On one server it's mounting without problem but on second one failing with invalid argument error:
mount error(22): Invalid argument Refer to the mount.cifs(8) manual
page (e.g. man mount.cifs)
Executing same command on both servers:
mount -t cifs -o username=username,domain=domain-name //path/to/share
/mount/path
Kernel log write such messages:
[Tue Dec 4 13:48:36 2018] No dialect specified on mount. Default has
changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from
CIFS (SMB1). To use the less secure SMB1 dialect to access old servers
which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [Tue
Dec 4 13:48:36 2018] CIFS VFS: cifs_mount failed w/return code = -22
mount fstab cifs
asked Dec 4 at 12:00
Edgars
1
I have a two similar Ubuntu servers 18.04 (4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) and trying to mount windows files server share on it. On one server it's mounting without problem but on second one failing with invalid argument error:
mount error(22): Invalid argument Refer to the mount.cifs(8) manual
page (e.g. man mount.cifs)
Executing same command on both servers:
mount -t cifs -o username=username,domain=domain-name //path/to/share
/mount/path
Kernel log write such messages:
[Tue Dec 4 13:48:36 2018] No dialect specified on mount. Default has
changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from
CIFS (SMB1). To use the less secure SMB1 dialect to access old servers
which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [Tue
Dec 4 13:48:36 2018] CIFS VFS: cifs_mount failed w/return code = -22
mount fstab cifs
mount fstab cifs
asked Dec 4 at 12:00
Edgars
1
asked Dec 4 at 12:00
Edgars
1
asked Dec 4 at 12:00
Edgars
1
asked Dec 4 at 12:00
Edgars
1
asked Dec 4 at 12:00
Edgars
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The Kernel messeage says it: The default SMB dialect doesn't work and you have to specify it.
The MAN Page of mount.cifs explains the option:
vers=
SMB protocol version. Allowed values are:
· 1.0 - The classic CIFS/SMBv1 protocol. This is the default.
· 2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and Windows Server 2008. Note that the initial release version of
Windows Vista spoke a slightly different dialect (2.000) that is not supported.
· 2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.
· 3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.
Note too that while this option governs the protocol version used, not all features of each version are available.
So you should try to find out which SMB dialect your server is speaking and specify it in your command
Example:
mount -t cifs -o username=username,domain=domain-name,vers=1.0 //path/to/share /mount/path
Link to the man page for further reference: https://linux.die.net/man/8/mount.cifs
answered Dec 4 at 12:40
Benibr
1312
I have tried all protocol version but no one helped... same mount error.
– Edgars
Dec 4 at 12:59
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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',
autoActivateHeartbeat: false,
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%2faskubuntu.com%2fquestions%2f1098369%2fmount-cifs-problems-on-ubuntu-18-04%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
The Kernel messeage says it: The default SMB dialect doesn't work and you have to specify it.
The MAN Page of mount.cifs explains the option:
vers=
SMB protocol version. Allowed values are:
· 1.0 - The classic CIFS/SMBv1 protocol. This is the default.
· 2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and Windows Server 2008. Note that the initial release version of
Windows Vista spoke a slightly different dialect (2.000) that is not supported.
· 2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.
· 3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.
Note too that while this option governs the protocol version used, not all features of each version are available.
So you should try to find out which SMB dialect your server is speaking and specify it in your command
Example:
mount -t cifs -o username=username,domain=domain-name,vers=1.0 //path/to/share /mount/path
Link to the man page for further reference: https://linux.die.net/man/8/mount.cifs
answered Dec 4 at 12:40
Benibr
1312
I have tried all protocol version but no one helped... same mount error.
– Edgars
Dec 4 at 12:59
add a comment |
up vote
0
down vote
The Kernel messeage says it: The default SMB dialect doesn't work and you have to specify it.
The MAN Page of mount.cifs explains the option:
vers=
SMB protocol version. Allowed values are:
· 1.0 - The classic CIFS/SMBv1 protocol. This is the default.
· 2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and Windows Server 2008. Note that the initial release version of
Windows Vista spoke a slightly different dialect (2.000) that is not supported.
· 2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.
· 3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.
Note too that while this option governs the protocol version used, not all features of each version are available.
So you should try to find out which SMB dialect your server is speaking and specify it in your command
Example:
mount -t cifs -o username=username,domain=domain-name,vers=1.0 //path/to/share /mount/path
Link to the man page for further reference: https://linux.die.net/man/8/mount.cifs
answered Dec 4 at 12:40
Benibr
1312
I have tried all protocol version but no one helped... same mount error.
– Edgars
Dec 4 at 12:59
add a comment |
up vote
0
down vote
up vote
0
down vote
The Kernel messeage says it: The default SMB dialect doesn't work and you have to specify it.
The MAN Page of mount.cifs explains the option:
vers=
SMB protocol version. Allowed values are:
· 1.0 - The classic CIFS/SMBv1 protocol. This is the default.
· 2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and Windows Server 2008. Note that the initial release version of
Windows Vista spoke a slightly different dialect (2.000) that is not supported.
· 2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.
· 3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.
Note too that while this option governs the protocol version used, not all features of each version are available.
So you should try to find out which SMB dialect your server is speaking and specify it in your command
Example:
mount -t cifs -o username=username,domain=domain-name,vers=1.0 //path/to/share /mount/path
Link to the man page for further reference: https://linux.die.net/man/8/mount.cifs
answered Dec 4 at 12:40
Benibr
1312
The Kernel messeage says it: The default SMB dialect doesn't work and you have to specify it.
The MAN Page of mount.cifs explains the option:
vers=
SMB protocol version. Allowed values are:
· 1.0 - The classic CIFS/SMBv1 protocol. This is the default.
· 2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and Windows Server 2008. Note that the initial release version of
Windows Vista spoke a slightly different dialect (2.000) that is not supported.
· 2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.
· 3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.
Note too that while this option governs the protocol version used, not all features of each version are available.
So you should try to find out which SMB dialect your server is speaking and specify it in your command
Example:
mount -t cifs -o username=username,domain=domain-name,vers=1.0 //path/to/share /mount/path
Link to the man page for further reference: https://linux.die.net/man/8/mount.cifs
answered Dec 4 at 12:40
Benibr
1312
answered Dec 4 at 12:40
Benibr
1312
answered Dec 4 at 12:40
Benibr
1312
answered Dec 4 at 12:40
Benibr
1312
1312
I have tried all protocol version but no one helped... same mount error.
– Edgars
Dec 4 at 12:59
add a comment |
I have tried all protocol version but no one helped... same mount error.
– Edgars
Dec 4 at 12:59
I have tried all protocol version but no one helped... same mount error.
– Edgars
Dec 4 at 12:59
I have tried all protocol version but no one helped... same mount error.
– Edgars
Dec 4 at 12:59
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1098369%2fmount-cifs-problems-on-ubuntu-18-04%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
