After samba upgrade i cannot connect to samba share with \hostname or \FQDN but i can from IP. (Both way...












0















I can fully access my samba share with \ip from windows explorer but not with \hostname or \FQDN. Samba is running on centos 7.
This happened after an upgrade from 4.7 to 4.8.3.
We did the same upgrade on another server with the same result.



SSH connection using hostname or FQDN is working so it's not a DNS problem.
( adding to the ip to C:WindowsSystem32Driversetchosts doesn't change a thing)
I am not the only one who can't access the share, no one can access it with hostname.



When connected with ip, samba generate a log file with my laptop hostname but when i use my \hostname or \FQDN it create a log with my ip.
This log contain a lot of this line :



[2018/12/18 16:02:37.674939,  1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step)
gensec_spnego_server_negTokenInit_step: ntlmssp: parsing NEG_TOKEN_INIT content failed (next[(null)]): NT_STATUS_INVALID_PARAMETER


one funny thing, for a few time when i run this command on windows :



net use \SERVER /user:whatever


I was able to connect using hostname, but it only affected my computer and work only up to reboot.










share|improve this question



























    0















    I can fully access my samba share with \ip from windows explorer but not with \hostname or \FQDN. Samba is running on centos 7.
    This happened after an upgrade from 4.7 to 4.8.3.
    We did the same upgrade on another server with the same result.



    SSH connection using hostname or FQDN is working so it's not a DNS problem.
    ( adding to the ip to C:WindowsSystem32Driversetchosts doesn't change a thing)
    I am not the only one who can't access the share, no one can access it with hostname.



    When connected with ip, samba generate a log file with my laptop hostname but when i use my \hostname or \FQDN it create a log with my ip.
    This log contain a lot of this line :



    [2018/12/18 16:02:37.674939,  1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step)
    gensec_spnego_server_negTokenInit_step: ntlmssp: parsing NEG_TOKEN_INIT content failed (next[(null)]): NT_STATUS_INVALID_PARAMETER


    one funny thing, for a few time when i run this command on windows :



    net use \SERVER /user:whatever


    I was able to connect using hostname, but it only affected my computer and work only up to reboot.










    share|improve this question

























      0












      0








      0








      I can fully access my samba share with \ip from windows explorer but not with \hostname or \FQDN. Samba is running on centos 7.
      This happened after an upgrade from 4.7 to 4.8.3.
      We did the same upgrade on another server with the same result.



      SSH connection using hostname or FQDN is working so it's not a DNS problem.
      ( adding to the ip to C:WindowsSystem32Driversetchosts doesn't change a thing)
      I am not the only one who can't access the share, no one can access it with hostname.



      When connected with ip, samba generate a log file with my laptop hostname but when i use my \hostname or \FQDN it create a log with my ip.
      This log contain a lot of this line :



      [2018/12/18 16:02:37.674939,  1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step)
      gensec_spnego_server_negTokenInit_step: ntlmssp: parsing NEG_TOKEN_INIT content failed (next[(null)]): NT_STATUS_INVALID_PARAMETER


      one funny thing, for a few time when i run this command on windows :



      net use \SERVER /user:whatever


      I was able to connect using hostname, but it only affected my computer and work only up to reboot.










      share|improve this question














      I can fully access my samba share with \ip from windows explorer but not with \hostname or \FQDN. Samba is running on centos 7.
      This happened after an upgrade from 4.7 to 4.8.3.
      We did the same upgrade on another server with the same result.



      SSH connection using hostname or FQDN is working so it's not a DNS problem.
      ( adding to the ip to C:WindowsSystem32Driversetchosts doesn't change a thing)
      I am not the only one who can't access the share, no one can access it with hostname.



      When connected with ip, samba generate a log file with my laptop hostname but when i use my \hostname or \FQDN it create a log with my ip.
      This log contain a lot of this line :



      [2018/12/18 16:02:37.674939,  1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step)
      gensec_spnego_server_negTokenInit_step: ntlmssp: parsing NEG_TOKEN_INIT content failed (next[(null)]): NT_STATUS_INVALID_PARAMETER


      one funny thing, for a few time when i run this command on windows :



      net use \SERVER /user:whatever


      I was able to connect using hostname, but it only affected my computer and work only up to reboot.







      windows-10 samba






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 26 '18 at 14:19









      GY6GY6

      11




      11






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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%2fsuperuser.com%2fquestions%2f1387827%2fafter-samba-upgrade-i-cannot-connect-to-samba-share-with-hostname-or-fqdn-bu%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • 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%2fsuperuser.com%2fquestions%2f1387827%2fafter-samba-upgrade-i-cannot-connect-to-samba-share-with-hostname-or-fqdn-bu%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

          Сан-Квентин

          8-я гвардейская общевойсковая армия

          Алькесар