[Samba] unable to upload printer driver

Wed Jun 7 12:48:56 UTC 2017

Hello Franz,

Out of curisoity I tried to install the old Kyocera Universal drivers we 
use since a few years on an other samba server (4.6.5).
Found the old version here 
https://www.rz.uni-osnabrueck.de/fileadmin/user_upload/Campuscard/Drucken/Treiber/win8/KyoceraClassicUniversalDriversCertified130315.zip.
It also fails now and the OEMSETUP.INF file also contains an 
PrinterPackageInstallation.x86/amd64 section.
Once i remove these sections the drivers can be installed but are 
treated as unsigned.
These drivers could be installed fine when the servers ran samba 4.0/4.1.
I opened an bug in regards to the issue with the 
PrinterPackageInstallation sections 
https://bugzilla.samba.org/show_bug.cgi?id=12763.
Seems developers think they  must implement the new MS-PAR protocol. But 
the drivers would work if they'd just ignore these sections and install 
as version 3.

achim~

Am 07.06.2017 um 14:20 schrieb Franz Gansberger:
> Hi Achim,
>
> thank you for your effort!
> I did a couple of tests, from W8.1 with x64 driver which where rather 
> old and therefore disignated for W7x64. But this went stale as well.
> Therefore I'll give it a try by using a W7-WS for uploading the drivers.
>
> Franz
>
>
> >>> Achim Gottinger <achim at ag-web.biz> 06.06.2017 15:27 >>>
> Hmm after another try an windows 7 client 32 and 64 bit can install such
> an driver now. Sorry for the noise. :-)
>
>
> Am 06.06.2017 um 15:10 schrieb Achim Gottinger via samba:
> > Please ignore the recommendation, such an driver can not be assigned
> > to an printer.
> >
> > Am 06.06.2017 um 14:54 schrieb Achim Gottinger via samba:
> >> I can install Kyocera Universal KPDL drivers once i delete the 
> sections:
> >>
> >> [PrinterPackageInstallation.x86]
> >> PackageAware=TRUE
> >> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1}
> >>
> >> [PrinterPackageInstallation.amd64]
> >> PackageAware=TRUE
> >> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1}
> >>
> >> in the OEMSETUP.inf file.
> >>
> >> But editing the file invalidates signing.
> >>
> >> Am 06.06.2017 um 12:59 schrieb Franz Gansberger via samba:
> >>> Hi Louis,
> >>>
> >>> thank you for your answer.
> >>>
> >>> - the link was already there
> >>> - I followed this hints:
> >>> https://lists.samba.org/archive/samba/2016-November/204773.html
>
> >>> did the chmod 2775
> >>> administrator is part of the PrintOperatorGroup
> >>> net rpc rights list privileges SePrintOperatorPrivilege -U
> >>> "H955\administrator"
> >>>
> >>> getfacl printerdrivers
> >>> # file: printerdrivers
> >>> # owner: root
> >>> # group: H955\134domain\040admins
> >>> # flags: -s-
> >>> user::rwx
> >>> user:root:rwx
> >>> user:3000003:r-x
> >>> user:H955\134domain\040admins:rwx
> >>> group::rwx
> >>> group:3000003:r-x
> >>> group:H955\134domain\040admins:rwx
> >>> mask::rwx
> >>> other::---
> >>> default:user::rwx
> >>> default:user:root:rwx
> >>> default:user:3000003:r-x
> >>> default:user:H955\134domain\040admins:rwx
> >>> default:group::---
> >>> default:group:3000003:r-x
> >>> default:group:H955\134domain\040admins:rwx
> >>> default:mask::rwx
> >>> default:other::---
> >>>
> >>> Now I found this post:
> >>> 
> https://groups.google.com/forum/#!msg/linux.samba/9BptH0lYLSk/D7pBaYnoDgAJ 
> <https://groups.google.com/forum/#%21msg/linux.samba/9BptH0lYLSk/D7pBaYnoDgAJ> 
>
>
> >>>
> >>>
> >>> Herr I tried the printui /s /t2  - had an ver4.
> >>> Now I found an relative old driver for the Kyocera FS-C5150 (windows
> >>> 7 x64, ver3), and installed it successfully local.
> >>> But nontheless putting that on the share on samba failes again?!
> >>>
> >>> Also - some of the ancient driver (HP4050, HP4250) which are the
> >>> easyest one (did that manually on Samba 3.x years ago) also fail on
> >>> putting the driver remote for download.
> >>>
> >>> I'm trying this from a W8.1 WS
> >>>
> >>> Thanks!
> >>> Franz
> >>>
> >>>
> >>>>>> L.P.H. van Belle <belle at bazuin.nl> 04.06.2017 00:38 >>>
> >>>
> >>>> Op 1 jun. 2017 om 15:20 heeft Franz Gansberger via samba
> >>>> <samba at lists.samba.org> het volgende geschreven:
> >>>>
> >>>> Hi all,
> >>>>
> >>>> according to this thread, I ran into the same situation:
> >>>>
> >>>> [2017/06/01 10:35:46.909754,  0]
> >>>> 
> ../source3/rpc_server/spoolss/srv_spoolss_nt.c:8476(_spoolss_AddPrinterDriverEx)
> >>>>   _spoolss_AddPrinterDriverEx: level 8 not yet implemented
> >>>> [2017/06/01 10:35:46.925055,  0]
> >>>> 
> ../source3/printing/nt_printing.c:1097(move_driver_file_to_download_area)
> >>>>   move_driver_file_to_download_area: Unable to rename
> >>>> [x64/kmfc5150_xps] to [x64/3/KMFC5150_XPS]:
> >>>> NT_STATUS_OBJECT_NAME_NOT_FOUND
> >>>>
> >>>>
> >>>> [print$]
> >>>>        path = /data/data/printerdrivers/
> >>>>        read only = no
> >>>>       acl_xattr:ignore system acl = yes
> >>>>       browseable = yes
> >>>>       guest ok = no
> >>>>       write list = root, administrator, @"Domain Admins", @lpadmin,
> >>>> @"Print Operators"
> >>>>
> >>>>
> >>>> Samba version 4.5.8-Debian
> >>>>
> >>>> I followed all the hints from Rowland, but...
> >>>>
> >>>> Has there been any solution so far?
> >>>> Appreciate any thoughts..
> >>>> :-)
> >>>>
> >>>> Franz
> >>>> --
> >>>> To unsubscribe from this list go to the following URL and read the
> >>>> instructions: https://lists.samba.org/mailman/options/samba
>
> >>> if it a kyocera driver, you need to cleanup all 32bit parts from the
> >>> inf.
> >>>
> >>> and you can try
> >>> ln -s x64 X64 in the driver folder
> >>>
> >>> last xps driver? cant test this atm but try the pcl or ps version.
> >>>
> >>> there is a post of me which tells verything you need to know for a
> >>> printer (cups) set on debian. (google for it, use l.p.h in your 
> search)
> >>>
> >>> last, you only need the first three line if you use acl_xattr:ignore
> >>> system acl = yes
> >>> and configure the share from a windows client.
> >>>
> >>> dont mix posix acl settings and acl_xattr:ignore system acl = yes
> >>>
> >>> still no go after above, i can test next wednesday and give better
> >>> help.
> >>>
> >>> ps? that driver is it a 'level 3 Windows driver' since level 4 and
> >>> up are not supported yet.   ( the error msg shows level 8, but that
> >>> not the windows level)
> >>>
> >>> greetz
> >>>
> >>> Louis
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>
>