CIFS vs Windows Server 2012 R2 : error 13












0














I tried to mount manually on my Linux shared folders from windows server 2012 R2.



The syntaxe is right but Im stuck on the same issue error 13:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1
dmesg:
Status code returned 0xc000006d STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13


If I tried other vers= options I got the same issue.
If I remove the option vers= then syslog claim :



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.


If I use option sec= then I specify this option then I got error 126



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1,sec=krb5
mount error(126): Required key not available


Package Keyutils is installed.



If I tried other sec= options I got error 22 or error 13



if I tried to prompt the password:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk
Password for bob@dude-uk@//ip/division:
mount error(13): Permission denied


Nemo (file explorer in Linux Mint) can mount the shared folders.
MacOsx can mount shared folders.



My kernel is 4.13
Mount.cifs is 6.4
I tried to mount manually before setup my fstab.



Do you have any idea ?










share|improve this question






















  • Read the man page for mount.cifs. In particular for the user (username) parameter. Yours is wrong.
    – roaima
    Apr 20 '18 at 8:04










  • see unix.stackexchange.com/questions/367884/…
    – Rui F Ribeiro
    Apr 20 '18 at 10:30










  • I read that Windows 2012 uses vers=3.0.
    – Gerard H. Pille
    Apr 20 '18 at 11:31
















0














I tried to mount manually on my Linux shared folders from windows server 2012 R2.



The syntaxe is right but Im stuck on the same issue error 13:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1
dmesg:
Status code returned 0xc000006d STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13


If I tried other vers= options I got the same issue.
If I remove the option vers= then syslog claim :



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.


If I use option sec= then I specify this option then I got error 126



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1,sec=krb5
mount error(126): Required key not available


Package Keyutils is installed.



If I tried other sec= options I got error 22 or error 13



if I tried to prompt the password:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk
Password for bob@dude-uk@//ip/division:
mount error(13): Permission denied


Nemo (file explorer in Linux Mint) can mount the shared folders.
MacOsx can mount shared folders.



My kernel is 4.13
Mount.cifs is 6.4
I tried to mount manually before setup my fstab.



Do you have any idea ?










share|improve this question






















  • Read the man page for mount.cifs. In particular for the user (username) parameter. Yours is wrong.
    – roaima
    Apr 20 '18 at 8:04










  • see unix.stackexchange.com/questions/367884/…
    – Rui F Ribeiro
    Apr 20 '18 at 10:30










  • I read that Windows 2012 uses vers=3.0.
    – Gerard H. Pille
    Apr 20 '18 at 11:31














0












0








0







I tried to mount manually on my Linux shared folders from windows server 2012 R2.



The syntaxe is right but Im stuck on the same issue error 13:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1
dmesg:
Status code returned 0xc000006d STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13


If I tried other vers= options I got the same issue.
If I remove the option vers= then syslog claim :



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.


If I use option sec= then I specify this option then I got error 126



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1,sec=krb5
mount error(126): Required key not available


Package Keyutils is installed.



If I tried other sec= options I got error 22 or error 13



if I tried to prompt the password:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk
Password for bob@dude-uk@//ip/division:
mount error(13): Permission denied


Nemo (file explorer in Linux Mint) can mount the shared folders.
MacOsx can mount shared folders.



My kernel is 4.13
Mount.cifs is 6.4
I tried to mount manually before setup my fstab.



Do you have any idea ?










share|improve this question













I tried to mount manually on my Linux shared folders from windows server 2012 R2.



The syntaxe is right but Im stuck on the same issue error 13:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1
dmesg:
Status code returned 0xc000006d STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13


If I tried other vers= options I got the same issue.
If I remove the option vers= then syslog claim :



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.


If I use option sec= then I specify this option then I got error 126



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk,password=myscretpass,vers=2.1,sec=krb5
mount error(126): Required key not available


Package Keyutils is installed.



If I tried other sec= options I got error 22 or error 13



if I tried to prompt the password:



#mount.cifs //ip/division /mnt/division -o username=bob@dude-uk
Password for bob@dude-uk@//ip/division:
mount error(13): Permission denied


Nemo (file explorer in Linux Mint) can mount the shared folders.
MacOsx can mount shared folders.



My kernel is 4.13
Mount.cifs is 6.4
I tried to mount manually before setup my fstab.



Do you have any idea ?







windows cifs






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 20 '18 at 7:56









DragonF0rceDragonF0rce

13




13












  • Read the man page for mount.cifs. In particular for the user (username) parameter. Yours is wrong.
    – roaima
    Apr 20 '18 at 8:04










  • see unix.stackexchange.com/questions/367884/…
    – Rui F Ribeiro
    Apr 20 '18 at 10:30










  • I read that Windows 2012 uses vers=3.0.
    – Gerard H. Pille
    Apr 20 '18 at 11:31


















  • Read the man page for mount.cifs. In particular for the user (username) parameter. Yours is wrong.
    – roaima
    Apr 20 '18 at 8:04










  • see unix.stackexchange.com/questions/367884/…
    – Rui F Ribeiro
    Apr 20 '18 at 10:30










  • I read that Windows 2012 uses vers=3.0.
    – Gerard H. Pille
    Apr 20 '18 at 11:31
















Read the man page for mount.cifs. In particular for the user (username) parameter. Yours is wrong.
– roaima
Apr 20 '18 at 8:04




Read the man page for mount.cifs. In particular for the user (username) parameter. Yours is wrong.
– roaima
Apr 20 '18 at 8:04












see unix.stackexchange.com/questions/367884/…
– Rui F Ribeiro
Apr 20 '18 at 10:30




see unix.stackexchange.com/questions/367884/…
– Rui F Ribeiro
Apr 20 '18 at 10:30












I read that Windows 2012 uses vers=3.0.
– Gerard H. Pille
Apr 20 '18 at 11:31




I read that Windows 2012 uses vers=3.0.
– Gerard H. Pille
Apr 20 '18 at 11:31










3 Answers
3






active

oldest

votes


















0














After read Bugzilla:
bugzilla issue
Kernel 4.13 got an issue to use mount.cifs command properly.
I must boot on 4.12 kernel - I will update my post after that






share|improve this answer





























    0














    I create another user instead of use account administrator and it works !






    share|improve this answer





























      0














      I had the same error with the mount.cifs. I've used this line time and time again, but wouldn't work for a random reason.
      mount.cifs //server/domain_share /mnt -o user=admin,sec=ntlmsspi
      I tried the mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi and gave the same error. I attempted many variations of IPs and domain shares, and found that if I too away the DNS name and added the IP along with the suggested domain=domain_name.org I was able to get the access.
      The fix was
      mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi



      The authentication piece wouldn't allow me to input a Password with the DNS name of the server, had to go bare bones with the address and authentication to allow me access. Now that it's connected I can use the original line of code I've always used... Not sure about why the problem occurred, but there's the fix for my error (13).






      share|improve this answer








      New contributor




      SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.


















        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "106"
        };
        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: false,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        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
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438884%2fcifs-vs-windows-server-2012-r2-error-13%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









        0














        After read Bugzilla:
        bugzilla issue
        Kernel 4.13 got an issue to use mount.cifs command properly.
        I must boot on 4.12 kernel - I will update my post after that






        share|improve this answer


























          0














          After read Bugzilla:
          bugzilla issue
          Kernel 4.13 got an issue to use mount.cifs command properly.
          I must boot on 4.12 kernel - I will update my post after that






          share|improve this answer
























            0












            0








            0






            After read Bugzilla:
            bugzilla issue
            Kernel 4.13 got an issue to use mount.cifs command properly.
            I must boot on 4.12 kernel - I will update my post after that






            share|improve this answer












            After read Bugzilla:
            bugzilla issue
            Kernel 4.13 got an issue to use mount.cifs command properly.
            I must boot on 4.12 kernel - I will update my post after that







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 20 '18 at 8:48









            DragonF0rceDragonF0rce

            13




            13

























                0














                I create another user instead of use account administrator and it works !






                share|improve this answer


























                  0














                  I create another user instead of use account administrator and it works !






                  share|improve this answer
























                    0












                    0








                    0






                    I create another user instead of use account administrator and it works !






                    share|improve this answer












                    I create another user instead of use account administrator and it works !







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Apr 20 '18 at 14:33









                    DragonF0rceDragonF0rce

                    13




                    13























                        0














                        I had the same error with the mount.cifs. I've used this line time and time again, but wouldn't work for a random reason.
                        mount.cifs //server/domain_share /mnt -o user=admin,sec=ntlmsspi
                        I tried the mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi and gave the same error. I attempted many variations of IPs and domain shares, and found that if I too away the DNS name and added the IP along with the suggested domain=domain_name.org I was able to get the access.
                        The fix was
                        mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi



                        The authentication piece wouldn't allow me to input a Password with the DNS name of the server, had to go bare bones with the address and authentication to allow me access. Now that it's connected I can use the original line of code I've always used... Not sure about why the problem occurred, but there's the fix for my error (13).






                        share|improve this answer








                        New contributor




                        SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.























                          0














                          I had the same error with the mount.cifs. I've used this line time and time again, but wouldn't work for a random reason.
                          mount.cifs //server/domain_share /mnt -o user=admin,sec=ntlmsspi
                          I tried the mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi and gave the same error. I attempted many variations of IPs and domain shares, and found that if I too away the DNS name and added the IP along with the suggested domain=domain_name.org I was able to get the access.
                          The fix was
                          mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi



                          The authentication piece wouldn't allow me to input a Password with the DNS name of the server, had to go bare bones with the address and authentication to allow me access. Now that it's connected I can use the original line of code I've always used... Not sure about why the problem occurred, but there's the fix for my error (13).






                          share|improve this answer








                          New contributor




                          SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.





















                            0












                            0








                            0






                            I had the same error with the mount.cifs. I've used this line time and time again, but wouldn't work for a random reason.
                            mount.cifs //server/domain_share /mnt -o user=admin,sec=ntlmsspi
                            I tried the mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi and gave the same error. I attempted many variations of IPs and domain shares, and found that if I too away the DNS name and added the IP along with the suggested domain=domain_name.org I was able to get the access.
                            The fix was
                            mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi



                            The authentication piece wouldn't allow me to input a Password with the DNS name of the server, had to go bare bones with the address and authentication to allow me access. Now that it's connected I can use the original line of code I've always used... Not sure about why the problem occurred, but there's the fix for my error (13).






                            share|improve this answer








                            New contributor




                            SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            I had the same error with the mount.cifs. I've used this line time and time again, but wouldn't work for a random reason.
                            mount.cifs //server/domain_share /mnt -o user=admin,sec=ntlmsspi
                            I tried the mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi and gave the same error. I attempted many variations of IPs and domain shares, and found that if I too away the DNS name and added the IP along with the suggested domain=domain_name.org I was able to get the access.
                            The fix was
                            mount.cifs ///domain_share /mnt -o user=admin,domain=,sec=ntlmsspi



                            The authentication piece wouldn't allow me to input a Password with the DNS name of the server, had to go bare bones with the address and authentication to allow me access. Now that it's connected I can use the original line of code I've always used... Not sure about why the problem occurred, but there's the fix for my error (13).







                            share|improve this answer








                            New contributor




                            SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            share|improve this answer



                            share|improve this answer






                            New contributor




                            SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            answered 12 mins ago









                            SilentR4D4RSilentR4D4R

                            1




                            1




                            New contributor




                            SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.





                            New contributor





                            SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






                            SilentR4D4R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Unix & Linux Stack Exchange!


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




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438884%2fcifs-vs-windows-server-2012-r2-error-13%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

                                CARDNET

                                Boot-repair Failure: Unable to locate package grub-common:i386

                                濃尾地震