Mounting Windows Share using SMB 2.1 or greaterfstab SMB share not mounting with read write access to Windows 8 machineMounting windows share errorPermanent Windows share mountingProblem using SMB credentials file to mount SMB shareMounting CIFS Share per User using AutoFSHow do a mount a NAS (WD, MyBookLive) so i can add media to a plex server?mount cifs problems on ubuntu 18.04Issues Mounting CIFS Share using systemdMounting SMB share on Ubuntu 19.04

Why was LEGO reluctant to use additional colours for regular bricks in former times?

Approximation of homeomorphism by diffeomorphism

How to plot a uniform grid for a spatial and time domain using TikZ?

Creating 2020 in the fewest number of steps

Is it ethical to apply for a short-term grant with a partner/spouse/girlfriend?

Is there a difference between LASSO regularisation and LASSO penalisation?

Why are the 4th and 7th scale degrees removed from the major scale to make the Pentatonic scale?

Can this crack in the steel chain-side dropout be welded?

Is one spouse responsible if other failed to file taxes

Why there isn't public transport on Christmas Day in the UK

What's the difference between "men of violence" and "violent men"?

What is a Brown Bag Seminar?

Were ancient languages as sophisticated as modern languages?

How Much Would a Language Change Over 500 Years Completely Cut Off From Its Source?

What is the moral difference between abortion and infanticide?

Does adamantium solve the giant mecha problem?

Should I take a side in an external player conflict, or let my game die?

find ".ts" but not ".d.ts"

Security implication if android app can be installed on emulator

Java OOP Temperature Converter

How exactly did the separation between Saturn V stage 3 and the Command / Lunar Module work?

Toxic culture - I'm putting in more resources to help the project move faster, but people are slowing down

Where do "magic" hashing constants like 0x9e3779b9 and 0x9e3779b1 come from?

The use of ''riddle' in this context



Mounting Windows Share using SMB 2.1 or greater


fstab SMB share not mounting with read write access to Windows 8 machineMounting windows share errorPermanent Windows share mountingProblem using SMB credentials file to mount SMB shareMounting CIFS Share per User using AutoFSHow do a mount a NAS (WD, MyBookLive) so i can add media to a plex server?mount cifs problems on ubuntu 18.04Issues Mounting CIFS Share using systemdMounting SMB share on Ubuntu 19.04






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









11


















I am attempting to mount a Windows hosted SMB share (CIFS) using Ubuntu 12.04 (using kernel 3.13.0-117-generic). Mounting with SMB1 works, but that is not acceptable, we must instead mount with SMB2.1 or higher.



Below is the output from my attempts to do this by passing the ver= argument



root@----:/# mount -t cifs //SERVER/smbtest /mnt/smbtest --verbose -o ver=2.1,user=administrator
Password:
mount.cifs kernel mount options:
ip=10.16.0.40,unc=\server.domain.netsmbtest,ver=2.1,ver=1,user=administrator,pass=********
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


As you can see, there are two ver arguments in the mount.cifs kernel mount options, the one that I specified, and the default (1). This happens if I specify anything other than 1 or 1.0 for ver.



cifs-utils version 5.1 is installed, and cifs.ko is on version 2.02. From the SMB3 kernel status page on the Samba wiki, https://wiki.samba.org/index.php/SMB3_kernel_status,



"The minimum version for use of the Linux kernel SMB3 support is kernel version 3.12 (or backport of cifs.ko module version 2.02 or later) but kernel version 3.18 or later (or equivalent, ie cifs module version 2.04 or later) is recommended for best SMB3 support."


Can anyone help get me on the right track here? I must be missing something. What other methods are available to force SMB2+ connections? This is my first post here, and I tried to keep it brief, if I missed anything let me know and I'll add the info to my post.



As far as I can tell this should work, though I wouldn't be surprised if I have misunderstood something and SMB2+ isn't supported.



Thanks



EDIT: I understand 12.04 is EOL. I will update this post tomorrow with the relevant info for 14.04, which has the same issue. If anyone can answer re: 12.04, that would still be appreciated.










share|improve this question






















  • 1





    This is particularly relevant in lieu of wannacry ransom ware exploit targets SMB1

    – Jeff Puckett
    May 20 '17 at 23:10












  • If you have the device's name (e.g. foo) but not its ipaddr : nmblookup foo

    – phreed
    Oct 30 '18 at 16:01

















11


















I am attempting to mount a Windows hosted SMB share (CIFS) using Ubuntu 12.04 (using kernel 3.13.0-117-generic). Mounting with SMB1 works, but that is not acceptable, we must instead mount with SMB2.1 or higher.



Below is the output from my attempts to do this by passing the ver= argument



root@----:/# mount -t cifs //SERVER/smbtest /mnt/smbtest --verbose -o ver=2.1,user=administrator
Password:
mount.cifs kernel mount options:
ip=10.16.0.40,unc=\server.domain.netsmbtest,ver=2.1,ver=1,user=administrator,pass=********
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


As you can see, there are two ver arguments in the mount.cifs kernel mount options, the one that I specified, and the default (1). This happens if I specify anything other than 1 or 1.0 for ver.



cifs-utils version 5.1 is installed, and cifs.ko is on version 2.02. From the SMB3 kernel status page on the Samba wiki, https://wiki.samba.org/index.php/SMB3_kernel_status,



"The minimum version for use of the Linux kernel SMB3 support is kernel version 3.12 (or backport of cifs.ko module version 2.02 or later) but kernel version 3.18 or later (or equivalent, ie cifs module version 2.04 or later) is recommended for best SMB3 support."


Can anyone help get me on the right track here? I must be missing something. What other methods are available to force SMB2+ connections? This is my first post here, and I tried to keep it brief, if I missed anything let me know and I'll add the info to my post.



As far as I can tell this should work, though I wouldn't be surprised if I have misunderstood something and SMB2+ isn't supported.



Thanks



EDIT: I understand 12.04 is EOL. I will update this post tomorrow with the relevant info for 14.04, which has the same issue. If anyone can answer re: 12.04, that would still be appreciated.










share|improve this question






















  • 1





    This is particularly relevant in lieu of wannacry ransom ware exploit targets SMB1

    – Jeff Puckett
    May 20 '17 at 23:10












  • If you have the device's name (e.g. foo) but not its ipaddr : nmblookup foo

    – phreed
    Oct 30 '18 at 16:01













11













11









11








I am attempting to mount a Windows hosted SMB share (CIFS) using Ubuntu 12.04 (using kernel 3.13.0-117-generic). Mounting with SMB1 works, but that is not acceptable, we must instead mount with SMB2.1 or higher.



Below is the output from my attempts to do this by passing the ver= argument



root@----:/# mount -t cifs //SERVER/smbtest /mnt/smbtest --verbose -o ver=2.1,user=administrator
Password:
mount.cifs kernel mount options:
ip=10.16.0.40,unc=\server.domain.netsmbtest,ver=2.1,ver=1,user=administrator,pass=********
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


As you can see, there are two ver arguments in the mount.cifs kernel mount options, the one that I specified, and the default (1). This happens if I specify anything other than 1 or 1.0 for ver.



cifs-utils version 5.1 is installed, and cifs.ko is on version 2.02. From the SMB3 kernel status page on the Samba wiki, https://wiki.samba.org/index.php/SMB3_kernel_status,



"The minimum version for use of the Linux kernel SMB3 support is kernel version 3.12 (or backport of cifs.ko module version 2.02 or later) but kernel version 3.18 or later (or equivalent, ie cifs module version 2.04 or later) is recommended for best SMB3 support."


Can anyone help get me on the right track here? I must be missing something. What other methods are available to force SMB2+ connections? This is my first post here, and I tried to keep it brief, if I missed anything let me know and I'll add the info to my post.



As far as I can tell this should work, though I wouldn't be surprised if I have misunderstood something and SMB2+ isn't supported.



Thanks



EDIT: I understand 12.04 is EOL. I will update this post tomorrow with the relevant info for 14.04, which has the same issue. If anyone can answer re: 12.04, that would still be appreciated.










share|improve this question
















I am attempting to mount a Windows hosted SMB share (CIFS) using Ubuntu 12.04 (using kernel 3.13.0-117-generic). Mounting with SMB1 works, but that is not acceptable, we must instead mount with SMB2.1 or higher.



Below is the output from my attempts to do this by passing the ver= argument



root@----:/# mount -t cifs //SERVER/smbtest /mnt/smbtest --verbose -o ver=2.1,user=administrator
Password:
mount.cifs kernel mount options:
ip=10.16.0.40,unc=\server.domain.netsmbtest,ver=2.1,ver=1,user=administrator,pass=********
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


As you can see, there are two ver arguments in the mount.cifs kernel mount options, the one that I specified, and the default (1). This happens if I specify anything other than 1 or 1.0 for ver.



cifs-utils version 5.1 is installed, and cifs.ko is on version 2.02. From the SMB3 kernel status page on the Samba wiki, https://wiki.samba.org/index.php/SMB3_kernel_status,



"The minimum version for use of the Linux kernel SMB3 support is kernel version 3.12 (or backport of cifs.ko module version 2.02 or later) but kernel version 3.18 or later (or equivalent, ie cifs module version 2.04 or later) is recommended for best SMB3 support."


Can anyone help get me on the right track here? I must be missing something. What other methods are available to force SMB2+ connections? This is my first post here, and I tried to keep it brief, if I missed anything let me know and I'll add the info to my post.



As far as I can tell this should work, though I wouldn't be surprised if I have misunderstood something and SMB2+ isn't supported.



Thanks



EDIT: I understand 12.04 is EOL. I will update this post tomorrow with the relevant info for 14.04, which has the same issue. If anyone can answer re: 12.04, that would still be appreciated.







security file-sharing cifs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 17 '17 at 4:22







Oliver Vollmer

















asked May 16 '17 at 19:09









Oliver VollmerOliver Vollmer

1111 gold badge1 silver badge7 bronze badges




1111 gold badge1 silver badge7 bronze badges










  • 1





    This is particularly relevant in lieu of wannacry ransom ware exploit targets SMB1

    – Jeff Puckett
    May 20 '17 at 23:10












  • If you have the device's name (e.g. foo) but not its ipaddr : nmblookup foo

    – phreed
    Oct 30 '18 at 16:01












  • 1





    This is particularly relevant in lieu of wannacry ransom ware exploit targets SMB1

    – Jeff Puckett
    May 20 '17 at 23:10












  • If you have the device's name (e.g. foo) but not its ipaddr : nmblookup foo

    – phreed
    Oct 30 '18 at 16:01







1




1





This is particularly relevant in lieu of wannacry ransom ware exploit targets SMB1

– Jeff Puckett
May 20 '17 at 23:10






This is particularly relevant in lieu of wannacry ransom ware exploit targets SMB1

– Jeff Puckett
May 20 '17 at 23:10














If you have the device's name (e.g. foo) but not its ipaddr : nmblookup foo

– phreed
Oct 30 '18 at 16:01





If you have the device's name (e.g. foo) but not its ipaddr : nmblookup foo

– phreed
Oct 30 '18 at 16:01










3 Answers
3






active

oldest

votes


















6



















If I use ver, it realy types "Invalid argument"
but
man mount.cifs says that the option name is "vers", not "ver".



 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....


it works for me in Mint 18.1:



mount -t cifs //192.168.1.1/public /home/user/Desktop/share --verbose -o vers=2.1,user=winuser





share|improve this answer
































    0



















    I found the available options in my local man page. Check this on your own machine to see what it supports. Once in the man page, type /vers= to find that argument quickly.



    man mount.cifs


    I then mounted my share as follows:



    sudo mount -t cifs //nas/homes/mike /media/mike/nashome -o vers=3.11,credentials=/home/mike/.ssh/.smb_nas


    This required a credentials file with the following contents at /home/mike/.ssh/.smb_nas so I don't need to enter my password in the command (causing it to be stored in your command history in plain-text) or at the prompt (a nuisance).



    username=mike
    password=[REAL PASSWORD]
    domain=WORKGROUP


    I am mounting from a Synology NAS that supports SMB version 3.11. You would have to check your Windows (or whatever's hosting files via CIFS/SMB) version to see what it supports on the server-side.






    share|improve this answer
































      0



















      Oddly enough, if the share computer is not on that IP address, you might get this same error. A change to the DHCP "moved" our NAS and that was the root of my problem. Once the share was back on the proper IP, errors stopped.






      share|improve this answer


























        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/4.0/"u003ecc by-sa 4.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
        );



        );














        draft saved

        draft discarded
















        StackExchange.ready(
        function ()
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f915856%2fmounting-windows-share-using-smb-2-1-or-greater%23new-answer', 'question_page');

        );

        Post as a guest















        Required, but never shown


























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        6



















        If I use ver, it realy types "Invalid argument"
        but
        man mount.cifs says that the option name is "vers", not "ver".



         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....


        it works for me in Mint 18.1:



        mount -t cifs //192.168.1.1/public /home/user/Desktop/share --verbose -o vers=2.1,user=winuser





        share|improve this answer





























          6



















          If I use ver, it realy types "Invalid argument"
          but
          man mount.cifs says that the option name is "vers", not "ver".



           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....


          it works for me in Mint 18.1:



          mount -t cifs //192.168.1.1/public /home/user/Desktop/share --verbose -o vers=2.1,user=winuser





          share|improve this answer



























            6















            6











            6









            If I use ver, it realy types "Invalid argument"
            but
            man mount.cifs says that the option name is "vers", not "ver".



             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....


            it works for me in Mint 18.1:



            mount -t cifs //192.168.1.1/public /home/user/Desktop/share --verbose -o vers=2.1,user=winuser





            share|improve this answer














            If I use ver, it realy types "Invalid argument"
            but
            man mount.cifs says that the option name is "vers", not "ver".



             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....


            it works for me in Mint 18.1:



            mount -t cifs //192.168.1.1/public /home/user/Desktop/share --verbose -o vers=2.1,user=winuser






            share|improve this answer













            share|improve this answer




            share|improve this answer










            answered Jun 2 '17 at 10:16









            deadheaddeadhead

            691 bronze badge




            691 bronze badge


























                0



















                I found the available options in my local man page. Check this on your own machine to see what it supports. Once in the man page, type /vers= to find that argument quickly.



                man mount.cifs


                I then mounted my share as follows:



                sudo mount -t cifs //nas/homes/mike /media/mike/nashome -o vers=3.11,credentials=/home/mike/.ssh/.smb_nas


                This required a credentials file with the following contents at /home/mike/.ssh/.smb_nas so I don't need to enter my password in the command (causing it to be stored in your command history in plain-text) or at the prompt (a nuisance).



                username=mike
                password=[REAL PASSWORD]
                domain=WORKGROUP


                I am mounting from a Synology NAS that supports SMB version 3.11. You would have to check your Windows (or whatever's hosting files via CIFS/SMB) version to see what it supports on the server-side.






                share|improve this answer





























                  0



















                  I found the available options in my local man page. Check this on your own machine to see what it supports. Once in the man page, type /vers= to find that argument quickly.



                  man mount.cifs


                  I then mounted my share as follows:



                  sudo mount -t cifs //nas/homes/mike /media/mike/nashome -o vers=3.11,credentials=/home/mike/.ssh/.smb_nas


                  This required a credentials file with the following contents at /home/mike/.ssh/.smb_nas so I don't need to enter my password in the command (causing it to be stored in your command history in plain-text) or at the prompt (a nuisance).



                  username=mike
                  password=[REAL PASSWORD]
                  domain=WORKGROUP


                  I am mounting from a Synology NAS that supports SMB version 3.11. You would have to check your Windows (or whatever's hosting files via CIFS/SMB) version to see what it supports on the server-side.






                  share|improve this answer



























                    0















                    0











                    0









                    I found the available options in my local man page. Check this on your own machine to see what it supports. Once in the man page, type /vers= to find that argument quickly.



                    man mount.cifs


                    I then mounted my share as follows:



                    sudo mount -t cifs //nas/homes/mike /media/mike/nashome -o vers=3.11,credentials=/home/mike/.ssh/.smb_nas


                    This required a credentials file with the following contents at /home/mike/.ssh/.smb_nas so I don't need to enter my password in the command (causing it to be stored in your command history in plain-text) or at the prompt (a nuisance).



                    username=mike
                    password=[REAL PASSWORD]
                    domain=WORKGROUP


                    I am mounting from a Synology NAS that supports SMB version 3.11. You would have to check your Windows (or whatever's hosting files via CIFS/SMB) version to see what it supports on the server-side.






                    share|improve this answer














                    I found the available options in my local man page. Check this on your own machine to see what it supports. Once in the man page, type /vers= to find that argument quickly.



                    man mount.cifs


                    I then mounted my share as follows:



                    sudo mount -t cifs //nas/homes/mike /media/mike/nashome -o vers=3.11,credentials=/home/mike/.ssh/.smb_nas


                    This required a credentials file with the following contents at /home/mike/.ssh/.smb_nas so I don't need to enter my password in the command (causing it to be stored in your command history in plain-text) or at the prompt (a nuisance).



                    username=mike
                    password=[REAL PASSWORD]
                    domain=WORKGROUP


                    I am mounting from a Synology NAS that supports SMB version 3.11. You would have to check your Windows (or whatever's hosting files via CIFS/SMB) version to see what it supports on the server-side.







                    share|improve this answer













                    share|improve this answer




                    share|improve this answer










                    answered Jul 25 at 16:35









                    mightypilemightypile

                    5651 gold badge8 silver badges11 bronze badges




                    5651 gold badge8 silver badges11 bronze badges
























                        0



















                        Oddly enough, if the share computer is not on that IP address, you might get this same error. A change to the DHCP "moved" our NAS and that was the root of my problem. Once the share was back on the proper IP, errors stopped.






                        share|improve this answer





























                          0



















                          Oddly enough, if the share computer is not on that IP address, you might get this same error. A change to the DHCP "moved" our NAS and that was the root of my problem. Once the share was back on the proper IP, errors stopped.






                          share|improve this answer



























                            0















                            0











                            0









                            Oddly enough, if the share computer is not on that IP address, you might get this same error. A change to the DHCP "moved" our NAS and that was the root of my problem. Once the share was back on the proper IP, errors stopped.






                            share|improve this answer














                            Oddly enough, if the share computer is not on that IP address, you might get this same error. A change to the DHCP "moved" our NAS and that was the root of my problem. Once the share was back on the proper IP, errors stopped.







                            share|improve this answer













                            share|improve this answer




                            share|improve this answer










                            answered Oct 2 at 16:59









                            Chris KChris K

                            3133 silver badges12 bronze badges




                            3133 silver badges12 bronze badges































                                draft saved

                                draft discarded















































                                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.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function ()
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f915856%2fmounting-windows-share-using-smb-2-1-or-greater%23new-answer', 'question_page');

                                );

                                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









                                Popular posts from this blog

                                Tamil (spriik) Luke uk diar | Nawigatjuun

                                Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

                                Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?