samba print$ share won't allow driver upload from Windows machine












0















I am trying to use samba together with CUPS to share printers and their drivers for Windows machines in the network.
Every time I try to upload Printer drivers from a Windows 10 machine via the printmanagement.msc I get an "Access Denied" error, but on the server side I can see, that the files have been created!



I have so far installed samba on an Ubuntu 18.04 LTS workstation, created a samba user "root" with a corresponding password and edited the smb.conf



[print$]
path = /srv/samba/printer_drivers/
read only = no
guest ok = yes
browseable = yes
wirteable = yes
directory mask = 0775
create mask = 0775
write list = @lpadmin, root
admin users = @lpadmin, root
force user = root


the shared directory /srv/samba/printer_drivers/ has the following permissions:



root$ ls -la /srv/samba/printer_drivers/
total 36
drwxrwsr-x 9 root root 4096 Nov 7 14:30 ./
drwxr-xr-x 3 root root 4096 Nov 5 10:24 ../
drwxrwsr-x 2 root root 4096 Nov 7 14:30 IA64/
drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32ALPHA/
drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32MIPS/
drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32PPC/
drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32X86/
drwxrwsr-x 2 root root 4096 Nov 7 14:30 WIN40/
drwxrwsr-x 4 root root 4096 Nov 8 10:41 x64/


The subdirectories were automatically created by the Windows AddDriver Wizard



I connect the share on the Windows host via



net use x: \hostnameprint$ /user:root


I then enter the password which is accepted



the command completed successfully


I can then navigate to the share in windows explorer and create, modify and delete files without any problems.
When I open up printmanagement.msc, click on my samba server (which I added as printserver) and select "Add Driver" I am able to select a driver from the list, and click "Finish". I can then see an explorer file-transfer window that shows the files are being copied, and an ls of the shared directory on the Linux machine shows the files are there, but the windows machine then Throws an error:



"A driver HP LaserJet (...), Type 4 - Usermode x64 could not be installed. Access is denied."



As soon as I accept the error message with the OK button the driver files on the share are deleted.



The output of smbstatus (first 3 ip-address parts generalized by me):



root$ smbstatus
Samba version 4.7.6-Ubuntu
PID Username Group Machine Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
13162 root root *.*.*.119 (ipv4:*.*.*.119:49176) SMB3_11 - partial(AES-128-CMAC)

Service pid Machine Connected at Encryption Signing
---------------------------------------------------------------------------------------------
print$ 13162 *.*.*.119 Thu Nov 8 12:45:30 PM 2018 CET - -
IPC$ 13162 *.*.*.119 Thu Nov 8 12:45:37 PM 2018 CET - -

Locked files:
Pid Uid DenyMode Access R/W Oplock SharePath Name Time
--------------------------------------------------------------------------------------------------
13162 0 DENY_NONE 0x80 RDONLY NONE /srv/samba/printer_drivers . Thu Nov 8 12:45:31 2018









share|improve this question





























    0















    I am trying to use samba together with CUPS to share printers and their drivers for Windows machines in the network.
    Every time I try to upload Printer drivers from a Windows 10 machine via the printmanagement.msc I get an "Access Denied" error, but on the server side I can see, that the files have been created!



    I have so far installed samba on an Ubuntu 18.04 LTS workstation, created a samba user "root" with a corresponding password and edited the smb.conf



    [print$]
    path = /srv/samba/printer_drivers/
    read only = no
    guest ok = yes
    browseable = yes
    wirteable = yes
    directory mask = 0775
    create mask = 0775
    write list = @lpadmin, root
    admin users = @lpadmin, root
    force user = root


    the shared directory /srv/samba/printer_drivers/ has the following permissions:



    root$ ls -la /srv/samba/printer_drivers/
    total 36
    drwxrwsr-x 9 root root 4096 Nov 7 14:30 ./
    drwxr-xr-x 3 root root 4096 Nov 5 10:24 ../
    drwxrwsr-x 2 root root 4096 Nov 7 14:30 IA64/
    drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32ALPHA/
    drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32MIPS/
    drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32PPC/
    drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32X86/
    drwxrwsr-x 2 root root 4096 Nov 7 14:30 WIN40/
    drwxrwsr-x 4 root root 4096 Nov 8 10:41 x64/


    The subdirectories were automatically created by the Windows AddDriver Wizard



    I connect the share on the Windows host via



    net use x: \hostnameprint$ /user:root


    I then enter the password which is accepted



    the command completed successfully


    I can then navigate to the share in windows explorer and create, modify and delete files without any problems.
    When I open up printmanagement.msc, click on my samba server (which I added as printserver) and select "Add Driver" I am able to select a driver from the list, and click "Finish". I can then see an explorer file-transfer window that shows the files are being copied, and an ls of the shared directory on the Linux machine shows the files are there, but the windows machine then Throws an error:



    "A driver HP LaserJet (...), Type 4 - Usermode x64 could not be installed. Access is denied."



    As soon as I accept the error message with the OK button the driver files on the share are deleted.



    The output of smbstatus (first 3 ip-address parts generalized by me):



    root$ smbstatus
    Samba version 4.7.6-Ubuntu
    PID Username Group Machine Protocol Version Encryption Signing
    ----------------------------------------------------------------------------------------------------------------------------------------
    13162 root root *.*.*.119 (ipv4:*.*.*.119:49176) SMB3_11 - partial(AES-128-CMAC)

    Service pid Machine Connected at Encryption Signing
    ---------------------------------------------------------------------------------------------
    print$ 13162 *.*.*.119 Thu Nov 8 12:45:30 PM 2018 CET - -
    IPC$ 13162 *.*.*.119 Thu Nov 8 12:45:37 PM 2018 CET - -

    Locked files:
    Pid Uid DenyMode Access R/W Oplock SharePath Name Time
    --------------------------------------------------------------------------------------------------
    13162 0 DENY_NONE 0x80 RDONLY NONE /srv/samba/printer_drivers . Thu Nov 8 12:45:31 2018









    share|improve this question



























      0












      0








      0


      1






      I am trying to use samba together with CUPS to share printers and their drivers for Windows machines in the network.
      Every time I try to upload Printer drivers from a Windows 10 machine via the printmanagement.msc I get an "Access Denied" error, but on the server side I can see, that the files have been created!



      I have so far installed samba on an Ubuntu 18.04 LTS workstation, created a samba user "root" with a corresponding password and edited the smb.conf



      [print$]
      path = /srv/samba/printer_drivers/
      read only = no
      guest ok = yes
      browseable = yes
      wirteable = yes
      directory mask = 0775
      create mask = 0775
      write list = @lpadmin, root
      admin users = @lpadmin, root
      force user = root


      the shared directory /srv/samba/printer_drivers/ has the following permissions:



      root$ ls -la /srv/samba/printer_drivers/
      total 36
      drwxrwsr-x 9 root root 4096 Nov 7 14:30 ./
      drwxr-xr-x 3 root root 4096 Nov 5 10:24 ../
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 IA64/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32ALPHA/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32MIPS/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32PPC/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32X86/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 WIN40/
      drwxrwsr-x 4 root root 4096 Nov 8 10:41 x64/


      The subdirectories were automatically created by the Windows AddDriver Wizard



      I connect the share on the Windows host via



      net use x: \hostnameprint$ /user:root


      I then enter the password which is accepted



      the command completed successfully


      I can then navigate to the share in windows explorer and create, modify and delete files without any problems.
      When I open up printmanagement.msc, click on my samba server (which I added as printserver) and select "Add Driver" I am able to select a driver from the list, and click "Finish". I can then see an explorer file-transfer window that shows the files are being copied, and an ls of the shared directory on the Linux machine shows the files are there, but the windows machine then Throws an error:



      "A driver HP LaserJet (...), Type 4 - Usermode x64 could not be installed. Access is denied."



      As soon as I accept the error message with the OK button the driver files on the share are deleted.



      The output of smbstatus (first 3 ip-address parts generalized by me):



      root$ smbstatus
      Samba version 4.7.6-Ubuntu
      PID Username Group Machine Protocol Version Encryption Signing
      ----------------------------------------------------------------------------------------------------------------------------------------
      13162 root root *.*.*.119 (ipv4:*.*.*.119:49176) SMB3_11 - partial(AES-128-CMAC)

      Service pid Machine Connected at Encryption Signing
      ---------------------------------------------------------------------------------------------
      print$ 13162 *.*.*.119 Thu Nov 8 12:45:30 PM 2018 CET - -
      IPC$ 13162 *.*.*.119 Thu Nov 8 12:45:37 PM 2018 CET - -

      Locked files:
      Pid Uid DenyMode Access R/W Oplock SharePath Name Time
      --------------------------------------------------------------------------------------------------
      13162 0 DENY_NONE 0x80 RDONLY NONE /srv/samba/printer_drivers . Thu Nov 8 12:45:31 2018









      share|improve this question
















      I am trying to use samba together with CUPS to share printers and their drivers for Windows machines in the network.
      Every time I try to upload Printer drivers from a Windows 10 machine via the printmanagement.msc I get an "Access Denied" error, but on the server side I can see, that the files have been created!



      I have so far installed samba on an Ubuntu 18.04 LTS workstation, created a samba user "root" with a corresponding password and edited the smb.conf



      [print$]
      path = /srv/samba/printer_drivers/
      read only = no
      guest ok = yes
      browseable = yes
      wirteable = yes
      directory mask = 0775
      create mask = 0775
      write list = @lpadmin, root
      admin users = @lpadmin, root
      force user = root


      the shared directory /srv/samba/printer_drivers/ has the following permissions:



      root$ ls -la /srv/samba/printer_drivers/
      total 36
      drwxrwsr-x 9 root root 4096 Nov 7 14:30 ./
      drwxr-xr-x 3 root root 4096 Nov 5 10:24 ../
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 IA64/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32ALPHA/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32MIPS/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32PPC/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 W32X86/
      drwxrwsr-x 2 root root 4096 Nov 7 14:30 WIN40/
      drwxrwsr-x 4 root root 4096 Nov 8 10:41 x64/


      The subdirectories were automatically created by the Windows AddDriver Wizard



      I connect the share on the Windows host via



      net use x: \hostnameprint$ /user:root


      I then enter the password which is accepted



      the command completed successfully


      I can then navigate to the share in windows explorer and create, modify and delete files without any problems.
      When I open up printmanagement.msc, click on my samba server (which I added as printserver) and select "Add Driver" I am able to select a driver from the list, and click "Finish". I can then see an explorer file-transfer window that shows the files are being copied, and an ls of the shared directory on the Linux machine shows the files are there, but the windows machine then Throws an error:



      "A driver HP LaserJet (...), Type 4 - Usermode x64 could not be installed. Access is denied."



      As soon as I accept the error message with the OK button the driver files on the share are deleted.



      The output of smbstatus (first 3 ip-address parts generalized by me):



      root$ smbstatus
      Samba version 4.7.6-Ubuntu
      PID Username Group Machine Protocol Version Encryption Signing
      ----------------------------------------------------------------------------------------------------------------------------------------
      13162 root root *.*.*.119 (ipv4:*.*.*.119:49176) SMB3_11 - partial(AES-128-CMAC)

      Service pid Machine Connected at Encryption Signing
      ---------------------------------------------------------------------------------------------
      print$ 13162 *.*.*.119 Thu Nov 8 12:45:30 PM 2018 CET - -
      IPC$ 13162 *.*.*.119 Thu Nov 8 12:45:37 PM 2018 CET - -

      Locked files:
      Pid Uid DenyMode Access R/W Oplock SharePath Name Time
      --------------------------------------------------------------------------------------------------
      13162 0 DENY_NONE 0x80 RDONLY NONE /srv/samba/printer_drivers . Thu Nov 8 12:45:31 2018






      samba printer shared-folders






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 8 '18 at 22:59









      Rui F Ribeiro

      39.4k1479131




      39.4k1479131










      asked Nov 8 '18 at 12:37









      hummingbirdofwarhummingbirdofwar

      42




      42






















          1 Answer
          1






          active

          oldest

          votes


















          1














          You misspelled wirteable = yes, it should be writeable = yes, possibly that could fix it. But that is a wild guess, I just randomly stumbled upon.



          Also, testparm /etc/samba/smb.conf is your friend whenever you need to check for inconsistencies on your smb.conf file.






          share|improve this answer










          New contributor




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





















          • And since writeable = no is the default for smb.conf it's pretty possible that this misspelled word is what is causing the problem...

            – nwildner
            Jan 9 at 12:01











          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%2f480557%2fsamba-print-share-wont-allow-driver-upload-from-windows-machine%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









          1














          You misspelled wirteable = yes, it should be writeable = yes, possibly that could fix it. But that is a wild guess, I just randomly stumbled upon.



          Also, testparm /etc/samba/smb.conf is your friend whenever you need to check for inconsistencies on your smb.conf file.






          share|improve this answer










          New contributor




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





















          • And since writeable = no is the default for smb.conf it's pretty possible that this misspelled word is what is causing the problem...

            – nwildner
            Jan 9 at 12:01
















          1














          You misspelled wirteable = yes, it should be writeable = yes, possibly that could fix it. But that is a wild guess, I just randomly stumbled upon.



          Also, testparm /etc/samba/smb.conf is your friend whenever you need to check for inconsistencies on your smb.conf file.






          share|improve this answer










          New contributor




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





















          • And since writeable = no is the default for smb.conf it's pretty possible that this misspelled word is what is causing the problem...

            – nwildner
            Jan 9 at 12:01














          1












          1








          1







          You misspelled wirteable = yes, it should be writeable = yes, possibly that could fix it. But that is a wild guess, I just randomly stumbled upon.



          Also, testparm /etc/samba/smb.conf is your friend whenever you need to check for inconsistencies on your smb.conf file.






          share|improve this answer










          New contributor




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










          You misspelled wirteable = yes, it should be writeable = yes, possibly that could fix it. But that is a wild guess, I just randomly stumbled upon.



          Also, testparm /etc/samba/smb.conf is your friend whenever you need to check for inconsistencies on your smb.conf file.







          share|improve this answer










          New contributor




          Anon 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








          edited Jan 9 at 12:03









          nwildner

          14.1k14176




          14.1k14176






          New contributor




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









          answered Jan 9 at 11:26









          AnonAnon

          111




          111




          New contributor




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





          New contributor





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






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













          • And since writeable = no is the default for smb.conf it's pretty possible that this misspelled word is what is causing the problem...

            – nwildner
            Jan 9 at 12:01



















          • And since writeable = no is the default for smb.conf it's pretty possible that this misspelled word is what is causing the problem...

            – nwildner
            Jan 9 at 12:01

















          And since writeable = no is the default for smb.conf it's pretty possible that this misspelled word is what is causing the problem...

          – nwildner
          Jan 9 at 12:01





          And since writeable = no is the default for smb.conf it's pretty possible that this misspelled word is what is causing the problem...

          – nwildner
          Jan 9 at 12:01


















          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%2f480557%2fsamba-print-share-wont-allow-driver-upload-from-windows-machine%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

          How to make a Squid Proxy server?

          Is this a new Fibonacci Identity?

          Touch on Surface Book