Issues in accessing samba share on windows 10 onlysamba with OpenLDAP - NT_STATUS_NO_SUCH_USERChanging...

Can two figures have the same area, perimeter, and same number of segments have different shape?

Company requiring me to let them review research from before I was hired

"I you already know": is this proper English?

Should I leave my PhD after 3 years with a Masters?

What does the minus sign mean in measurements in datasheet footprint drawings?

A planet illuminated by a black hole?

What was the rationale behind 36 bit computer architectures?

Keeping an "hot eyeball planet" wet

Spoken encryption

Why are off grid solar setups only 12, 24, 48 VDC?

What is "ass door"?

How can I create a shape in Illustrator which follows a path in descending order size?

What is the purpose of the fuel shutoff valve?

This message is flooding my syslog, how to find where it comes from?

Is an easily guessed plot twist a good plot twist?

Terence Tao - type books in other fields?

What should I say when a company asks you why someone (a friend) who was fired left?

Why keep the bed heated after initial layer(s) with PLA (or PETG)?

How can I receive packages while in France?

Problem loading expl3 in plain TeX

Do Rabbis get punished in Heaven for wrong interpretations or claims?

Determine if a triangle is equilateral, isosceles, or scalene

Company messed up with patent and now a lawyer is coming after me

Spacing setting of math mode



Issues in accessing samba share on windows 10 only


samba with OpenLDAP - NT_STATUS_NO_SUCH_USERChanging Samba/LDAP password with passwdWindows creates autorun.inf when mounting samba shareUnable to access SAMBA Share From WindowsPublic share using sambaproblems with Samba shareCorrect syntax for mounting smbfs in FreeBSD?smb-share connection time increases each reboot on windows PECannot Access Samba Share on windows 10Linux clients can't login on samba share while windows and mac can (active directory env)






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







0















First diagnostics showed the following error:




windows socket registry entries missing




Then I have removed the registry entries of winsock and winsock2 and reinstalled them by downloading and ran the following command:



netsh winsock reset


Now, the diagnostics shows different error:




The device or resource (mysambashare.net) is not set up to
accept connections on port "The File and printer sharing (SMB)".




The samba logs shows this:




[2016/06/20 11:30:22.551172, 2]smbd/sesssetup.c:1413(setup_new_vc_session)



setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.



[2016/06/20 11:30:22.577394, 1]auth/auth_server.c:422(check_smbserver_security)



password server MYPASSWORDSERVER.NET rejected the password: NT_STATUS_INVALID_PARAMETER



[2016/06/20 11:30:22.593366, 2]auth/auth.c:314(check_ntlm_password)



check_ntlm_password: Authentication for user [jbehara] -> [jbehara] FAILED with error NT_STATUS_INVALID_PARAMETER .




The same above lines repeated 4 times continuously in samba logs.



No issues when I connect using the same credentials from another machine.



What could be the reason?










share|improve this question














bumped to the homepage by Community 41 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    See duplicate at superuser.com/questions/1091310/…

    – roaima
    Jun 24 '16 at 15:39






  • 1





    What version of Samba? What Linux-based distribution? Windows 10 or Windows 10 Professional? Can this Windows 10 client connect to any shares offered by a Windows server? Are your Windows client and Samba server domain joined? Please provide a copy of your smb.conf (redacted as appropriate).

    – roaima
    Jun 24 '16 at 15:41













  • If only one machine is affected, I wouldn't bother to try tracking it down. Reinstalling WIndows is the easiest solution; IMO there's just too many ways how a Windows can be damaged.

    – Martin von Wittich
    Jun 24 '16 at 21:21











  • Hi..I am currently not with my system...But any possible explanation in the meanwhile why samba show such error?

    – GP92
    Jun 24 '16 at 22:01




















0















First diagnostics showed the following error:




windows socket registry entries missing




Then I have removed the registry entries of winsock and winsock2 and reinstalled them by downloading and ran the following command:



netsh winsock reset


Now, the diagnostics shows different error:




The device or resource (mysambashare.net) is not set up to
accept connections on port "The File and printer sharing (SMB)".




The samba logs shows this:




[2016/06/20 11:30:22.551172, 2]smbd/sesssetup.c:1413(setup_new_vc_session)



setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.



[2016/06/20 11:30:22.577394, 1]auth/auth_server.c:422(check_smbserver_security)



password server MYPASSWORDSERVER.NET rejected the password: NT_STATUS_INVALID_PARAMETER



[2016/06/20 11:30:22.593366, 2]auth/auth.c:314(check_ntlm_password)



check_ntlm_password: Authentication for user [jbehara] -> [jbehara] FAILED with error NT_STATUS_INVALID_PARAMETER .




The same above lines repeated 4 times continuously in samba logs.



No issues when I connect using the same credentials from another machine.



What could be the reason?










share|improve this question














bumped to the homepage by Community 41 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    See duplicate at superuser.com/questions/1091310/…

    – roaima
    Jun 24 '16 at 15:39






  • 1





    What version of Samba? What Linux-based distribution? Windows 10 or Windows 10 Professional? Can this Windows 10 client connect to any shares offered by a Windows server? Are your Windows client and Samba server domain joined? Please provide a copy of your smb.conf (redacted as appropriate).

    – roaima
    Jun 24 '16 at 15:41













  • If only one machine is affected, I wouldn't bother to try tracking it down. Reinstalling WIndows is the easiest solution; IMO there's just too many ways how a Windows can be damaged.

    – Martin von Wittich
    Jun 24 '16 at 21:21











  • Hi..I am currently not with my system...But any possible explanation in the meanwhile why samba show such error?

    – GP92
    Jun 24 '16 at 22:01
















0












0








0


1






First diagnostics showed the following error:




windows socket registry entries missing




Then I have removed the registry entries of winsock and winsock2 and reinstalled them by downloading and ran the following command:



netsh winsock reset


Now, the diagnostics shows different error:




The device or resource (mysambashare.net) is not set up to
accept connections on port "The File and printer sharing (SMB)".




The samba logs shows this:




[2016/06/20 11:30:22.551172, 2]smbd/sesssetup.c:1413(setup_new_vc_session)



setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.



[2016/06/20 11:30:22.577394, 1]auth/auth_server.c:422(check_smbserver_security)



password server MYPASSWORDSERVER.NET rejected the password: NT_STATUS_INVALID_PARAMETER



[2016/06/20 11:30:22.593366, 2]auth/auth.c:314(check_ntlm_password)



check_ntlm_password: Authentication for user [jbehara] -> [jbehara] FAILED with error NT_STATUS_INVALID_PARAMETER .




The same above lines repeated 4 times continuously in samba logs.



No issues when I connect using the same credentials from another machine.



What could be the reason?










share|improve this question














First diagnostics showed the following error:




windows socket registry entries missing




Then I have removed the registry entries of winsock and winsock2 and reinstalled them by downloading and ran the following command:



netsh winsock reset


Now, the diagnostics shows different error:




The device or resource (mysambashare.net) is not set up to
accept connections on port "The File and printer sharing (SMB)".




The samba logs shows this:




[2016/06/20 11:30:22.551172, 2]smbd/sesssetup.c:1413(setup_new_vc_session)



setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.



[2016/06/20 11:30:22.577394, 1]auth/auth_server.c:422(check_smbserver_security)



password server MYPASSWORDSERVER.NET rejected the password: NT_STATUS_INVALID_PARAMETER



[2016/06/20 11:30:22.593366, 2]auth/auth.c:314(check_ntlm_password)



check_ntlm_password: Authentication for user [jbehara] -> [jbehara] FAILED with error NT_STATUS_INVALID_PARAMETER .




The same above lines repeated 4 times continuously in samba logs.



No issues when I connect using the same credentials from another machine.



What could be the reason?







samba






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jun 21 '16 at 6:27









GP92GP92

2492 gold badges8 silver badges22 bronze badges




2492 gold badges8 silver badges22 bronze badges





bumped to the homepage by Community 41 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 41 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 1





    See duplicate at superuser.com/questions/1091310/…

    – roaima
    Jun 24 '16 at 15:39






  • 1





    What version of Samba? What Linux-based distribution? Windows 10 or Windows 10 Professional? Can this Windows 10 client connect to any shares offered by a Windows server? Are your Windows client and Samba server domain joined? Please provide a copy of your smb.conf (redacted as appropriate).

    – roaima
    Jun 24 '16 at 15:41













  • If only one machine is affected, I wouldn't bother to try tracking it down. Reinstalling WIndows is the easiest solution; IMO there's just too many ways how a Windows can be damaged.

    – Martin von Wittich
    Jun 24 '16 at 21:21











  • Hi..I am currently not with my system...But any possible explanation in the meanwhile why samba show such error?

    – GP92
    Jun 24 '16 at 22:01
















  • 1





    See duplicate at superuser.com/questions/1091310/…

    – roaima
    Jun 24 '16 at 15:39






  • 1





    What version of Samba? What Linux-based distribution? Windows 10 or Windows 10 Professional? Can this Windows 10 client connect to any shares offered by a Windows server? Are your Windows client and Samba server domain joined? Please provide a copy of your smb.conf (redacted as appropriate).

    – roaima
    Jun 24 '16 at 15:41













  • If only one machine is affected, I wouldn't bother to try tracking it down. Reinstalling WIndows is the easiest solution; IMO there's just too many ways how a Windows can be damaged.

    – Martin von Wittich
    Jun 24 '16 at 21:21











  • Hi..I am currently not with my system...But any possible explanation in the meanwhile why samba show such error?

    – GP92
    Jun 24 '16 at 22:01










1




1





See duplicate at superuser.com/questions/1091310/…

– roaima
Jun 24 '16 at 15:39





See duplicate at superuser.com/questions/1091310/…

– roaima
Jun 24 '16 at 15:39




1




1





What version of Samba? What Linux-based distribution? Windows 10 or Windows 10 Professional? Can this Windows 10 client connect to any shares offered by a Windows server? Are your Windows client and Samba server domain joined? Please provide a copy of your smb.conf (redacted as appropriate).

– roaima
Jun 24 '16 at 15:41







What version of Samba? What Linux-based distribution? Windows 10 or Windows 10 Professional? Can this Windows 10 client connect to any shares offered by a Windows server? Are your Windows client and Samba server domain joined? Please provide a copy of your smb.conf (redacted as appropriate).

– roaima
Jun 24 '16 at 15:41















If only one machine is affected, I wouldn't bother to try tracking it down. Reinstalling WIndows is the easiest solution; IMO there's just too many ways how a Windows can be damaged.

– Martin von Wittich
Jun 24 '16 at 21:21





If only one machine is affected, I wouldn't bother to try tracking it down. Reinstalling WIndows is the easiest solution; IMO there's just too many ways how a Windows can be damaged.

– Martin von Wittich
Jun 24 '16 at 21:21













Hi..I am currently not with my system...But any possible explanation in the meanwhile why samba show such error?

– GP92
Jun 24 '16 at 22:01







Hi..I am currently not with my system...But any possible explanation in the meanwhile why samba show such error?

– GP92
Jun 24 '16 at 22:01












1 Answer
1






active

oldest

votes


















0














can you try to run : netsh interface ip reset C:resetlog.txt
on your windows machine, and tell us if it does fix your problem, and if not fixed, provide version of samba and answer to roaima comment :




What version of Samba? What Linux-based distribution? Windows 10 or
Windows 10 Professional? Can this Windows 10 client connect to any
shares offered by a Windows server? Are your Windows client and Samba
server domain joined? Please provide a copy of your smb.conf (redacted
as appropriate). – roaima







share|improve this answer


























    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%2f291064%2fissues-in-accessing-samba-share-on-windows-10-only%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









    0














    can you try to run : netsh interface ip reset C:resetlog.txt
    on your windows machine, and tell us if it does fix your problem, and if not fixed, provide version of samba and answer to roaima comment :




    What version of Samba? What Linux-based distribution? Windows 10 or
    Windows 10 Professional? Can this Windows 10 client connect to any
    shares offered by a Windows server? Are your Windows client and Samba
    server domain joined? Please provide a copy of your smb.conf (redacted
    as appropriate). – roaima







    share|improve this answer




























      0














      can you try to run : netsh interface ip reset C:resetlog.txt
      on your windows machine, and tell us if it does fix your problem, and if not fixed, provide version of samba and answer to roaima comment :




      What version of Samba? What Linux-based distribution? Windows 10 or
      Windows 10 Professional? Can this Windows 10 client connect to any
      shares offered by a Windows server? Are your Windows client and Samba
      server domain joined? Please provide a copy of your smb.conf (redacted
      as appropriate). – roaima







      share|improve this answer


























        0












        0








        0







        can you try to run : netsh interface ip reset C:resetlog.txt
        on your windows machine, and tell us if it does fix your problem, and if not fixed, provide version of samba and answer to roaima comment :




        What version of Samba? What Linux-based distribution? Windows 10 or
        Windows 10 Professional? Can this Windows 10 client connect to any
        shares offered by a Windows server? Are your Windows client and Samba
        server domain joined? Please provide a copy of your smb.conf (redacted
        as appropriate). – roaima







        share|improve this answer













        can you try to run : netsh interface ip reset C:resetlog.txt
        on your windows machine, and tell us if it does fix your problem, and if not fixed, provide version of samba and answer to roaima comment :




        What version of Samba? What Linux-based distribution? Windows 10 or
        Windows 10 Professional? Can this Windows 10 client connect to any
        shares offered by a Windows server? Are your Windows client and Samba
        server domain joined? Please provide a copy of your smb.conf (redacted
        as appropriate). – roaima








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 24 '16 at 20:31









        dominixdominix

        971 silver badge10 bronze badges




        971 silver badge10 bronze badges






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f291064%2fissues-in-accessing-samba-share-on-windows-10-only%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

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...