Windows is showing rpc server is unavailable when connecting to a SAMBA AD hosted on debian












-1














I have set up SAMBA to act as an AD DC and my machine connects to it fine but when I try to find the Active Directory tools from inside my windows machine I get the error 'naming information cannot be located because: the rpc server is unavailable'



I have no idea what thats bout and the few cases ive seen online deal in different situation not applicable to my case.










share|improve this question



























    -1














    I have set up SAMBA to act as an AD DC and my machine connects to it fine but when I try to find the Active Directory tools from inside my windows machine I get the error 'naming information cannot be located because: the rpc server is unavailable'



    I have no idea what thats bout and the few cases ive seen online deal in different situation not applicable to my case.










    share|improve this question

























      -1












      -1








      -1







      I have set up SAMBA to act as an AD DC and my machine connects to it fine but when I try to find the Active Directory tools from inside my windows machine I get the error 'naming information cannot be located because: the rpc server is unavailable'



      I have no idea what thats bout and the few cases ive seen online deal in different situation not applicable to my case.










      share|improve this question













      I have set up SAMBA to act as an AD DC and my machine connects to it fine but when I try to find the Active Directory tools from inside my windows machine I get the error 'naming information cannot be located because: the rpc server is unavailable'



      I have no idea what thats bout and the few cases ive seen online deal in different situation not applicable to my case.







      linux active-directory samba






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 '18 at 9:59









      RaRa

      12




      12
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The problem can be on either the client or server machine.



          Make sure Samba is listening on the right ports. RPC is on port 135. If you don't see Samba listening on port 135, then that's your problem.



          Also make sure that, on your client Windows machine, the "TCP/IP NetBIOS Helper" service is running (in services.msc) and set to run automatically. If that was not running, then that's your problem.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390443%2fwindows-is-showing-rpc-server-is-unavailable-when-connecting-to-a-samba-ad-hoste%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














            The problem can be on either the client or server machine.



            Make sure Samba is listening on the right ports. RPC is on port 135. If you don't see Samba listening on port 135, then that's your problem.



            Also make sure that, on your client Windows machine, the "TCP/IP NetBIOS Helper" service is running (in services.msc) and set to run automatically. If that was not running, then that's your problem.






            share|improve this answer


























              0














              The problem can be on either the client or server machine.



              Make sure Samba is listening on the right ports. RPC is on port 135. If you don't see Samba listening on port 135, then that's your problem.



              Also make sure that, on your client Windows machine, the "TCP/IP NetBIOS Helper" service is running (in services.msc) and set to run automatically. If that was not running, then that's your problem.






              share|improve this answer
























                0












                0








                0






                The problem can be on either the client or server machine.



                Make sure Samba is listening on the right ports. RPC is on port 135. If you don't see Samba listening on port 135, then that's your problem.



                Also make sure that, on your client Windows machine, the "TCP/IP NetBIOS Helper" service is running (in services.msc) and set to run automatically. If that was not running, then that's your problem.






                share|improve this answer












                The problem can be on either the client or server machine.



                Make sure Samba is listening on the right ports. RPC is on port 135. If you don't see Samba listening on port 135, then that's your problem.



                Also make sure that, on your client Windows machine, the "TCP/IP NetBIOS Helper" service is running (in services.msc) and set to run automatically. If that was not running, then that's your problem.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 20 '18 at 14:38









                Gabriel Luci

                10.4k11324




                10.4k11324






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • 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%2fstackoverflow.com%2fquestions%2f53390443%2fwindows-is-showing-rpc-server-is-unavailable-when-connecting-to-a-samba-ad-hoste%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