[Samba] Samba4 - Printer Drivers install fails

L. van Belle belle at samba.org
Fri Nov 22 16:11:57 UTC 2019


Hai guys, 

Update: 
I've just tested an upload of this driver with the printer manager in
windows. ( W7-x64 in this case ) 

impxeroxc405        imprimante Xerox Versalink c405 
To be exact : VersaLink_C400_5.658.3.0_PCL6_x64 
https://www.support.xerox.com/support/versalink-c405/file-download/enus.html
?operatingSystem=win10x64&fileLanguage=en&contentId=144414&from=downloads&vi
ewArchived=false
Which are Model 3 drivers as far i can tell. On my now 4.11.2 print server,
it also gave an error. 
Error code in windows : 0x0000023f  Then error, 0x00000578 

Im Monday in the proces that i must upgrade some of my printer drivers due
to a found bug in a kyocera driver.
Which makes a pdf print disapeer .. And not being printed. 
I'll write notes of the steps i'll do, and i hope we can find fix for it. 

@Samba Devs. 
i suspect this is something with signed/not signed SMB1/2/3 things. 

It might be related/looks like:
https://bugzilla.samba.org/show_bug.cgi?id=13093 

In addition to Julien logs below, i found these messages in daemon.log 

Nov 21 17:08:03 print1 smbd[707]: [2019/11/21 17:08:03.080421,  0] 
	
../../source3/printing/nt_printing.c:1462(move_driver_file_to_download_area)
Nov 21 17:08:03 print1 smbd[707]:   move_driver_file_to_download_area:
Unable to rename 
     [x64/{004398AB-A497-4700-90FD-59AD7F57D78E}/install_nbomx_xl_noredist] 
  to [x64/3/Install_NBOMX_XL_NoRedist]: NT_STATUS_OBJECT_NAME_NOT_FOUND

Nov 21 17:08:03 print1 smbd[707]: [2019/11/21 17:08:03.080582,  0]
../../source3/rpc_server/spoolss/srv_spoolss_nt.c:8621(_spoolss_AddPrinterDr
iverEx)
Nov 21 17:08:03 print1 smbd[707]:   _spoolss_AddPrinterDriverEx:
move_driver_to_download_area failed - WERR_APP_INIT_FAILURE

And this links back to :  https://bugzilla.samba.org/show_bug.cgi?id=13395  

Currently, we are unable to upload new drivers with the windows tools. 
I have not tried the commandline options yet, thats for Monday. 

So if one has ideas, of patches to test, let me know i'll test them. 

I also notice that MS had a "Point and Print Compatible driver" changes,
maybe this interfere.. 

The print server settings im using for completeness..

Normal Samba Member, backend AD. 
SePrivileges checked and set. 
verified with :
https://wiki.samba.org/index.php/Setting_up_Automatic_Printer_Driver_Downloa
ds_for_Windows_Clients 

##### PRINT SERVER PART #######
    #enable asu support = yes

    ## Enabling spoolssd
    rpc_server:spoolss = external
    rpc_daemon:spoolssd = fork
    spoolss:architecture = Windows x64
    spoolssd:prefork_min_children = 5           # Minimum number of child
processes
    spoolssd:prefork_max_children = 25          # Maximum number of child
processes
    spoolssd:prefork_spawn_rate = 5             # Start (fork) x new childs
if one connection comes in (up to prefork_max_children)
    spoolssd:prefork_max_allowed_clients = 100  # Number of clients, a child
process should be responsible for
    spoolssd:prefork_child_min_life = 60        # Minimum lifetime of a
child process (60 seconds
                                                # is the minimum, even a
lower value has been configured)
    load printers = yes

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /home/samba/printing/drivers
   acl_xattr:ignore system acl = yes
   browseable = yes
   writable = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
   write list = root, administrator, @"Domain Admins", @lpadmin, @"Print
Operators"

[printers]
   comment = All Printers
   path = /home/samba/printing/spool
   acl_xattr:ignore system acl = yes
   browseable = yes
   printable = yes
   printing = CUPS



WEEKEND... !  :-) 

Have a great weekend guys.. 

Greetz, 

Louis






> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Julien TEHERY via samba
> Verzonden: vrijdag 22 november 2019 15:15
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Samba4 - Printer Drivers install fails
> 
> 
> > FYI,
> >
> > I finally succeeded too upload one of the 3 drivers that 
> had problems.
> >
> > I didi it with another user (not  with administrator) which 
> is member 
> > of domain admins.
> >
> > I deleted it and tried so many times again to upload it anf 
> it failed 
> > with the same error.
> >
> > So we're in a process where sometimes it's working 
> sometimes not and 
> > you won't know why.
> >
> >
> > I'm still investigating, upgraded loglevel and saw this :
> >
> >
> > 2019/11/22 14:31:04.146325,  1] 
> > 
> ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
> >   Failed to fetch record!
> > [2019/11/22 14:31:25.108720,  2] 
> > ../source3/printing/spoolssd.c:459(spoolss_handle_client)
> >   Spoolss preforked child 11201 got client connection!
> > [2019/11/22 14:31:25.112839,  3] 
> > ../source3/rpc_server/srv_pipe.c:748(api_pipe_bind_req)
> >   api_pipe_bind_req: spoolss -> spoolss rpc service
> > [2019/11/22 14:31:25.112897,  3] 
> > ../source3/rpc_server/srv_pipe.c:356(check_bind_req)
> >   check_bind_req for spoolss context_id=0
> > [2019/11/22 14:31:25.112936,  3] 
> > ../source3/rpc_server/srv_pipe.c:399(check_bind_req)
> >   check_bind_req: spoolss -> spoolss rpc service
> > [2019/11/22 14:31:25.114898,  3] 
> > ../source3/rpc_server/srv_pipe.c:1528(api_rpcTNP)
> >   api_rpcTNP: rpc command: SPOOLSS_ADDPRINTERDRIVEREX
> > [2019/11/22 14:31:25.115252,  3] 
> > ../source3/smbd/vfs.c:113(vfs_init_default)
> >   Initialising default vfs hooks
> > [2019/11/22 14:31:25.115302,  3] 
> > ../source3/smbd/vfs.c:139(vfs_init_custom)
> >   Initialising custom vfs hooks from [/[Default VFS]/]
> > [2019/11/22 14:31:25.115329,  3] 
> > ../source3/smbd/vfs.c:139(vfs_init_custom)
> >   Initialising custom vfs hooks from [acl_xattr]
> > [2019/11/22 14:31:25.121499,  3] 
> > ../lib/util/modules.c:167(load_module_absolute_path)
> >   load_module_absolute_path: Module 
> > '/usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so' loaded
> > [2019/11/22 14:31:25.121567,  2] 
> > ../source3/modules/vfs_acl_xattr.c:236(connect_acl_xattr)
> >   connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = 
> > true' and 'force unknown acl user = true' for service print$
> > [2019/11/22 14:31:25.121861,  3] 
> > ../source3/lib/util.c:313(unix_clean_name)
> >   unix_clean_name [x64/3]
> > [2019/11/22 14:31:25.121920,  2] 
> > ../source3/smbd/open.c:3987(open_directory)
> >   open_directory: unable to create x64/3. Error was 
> > NT_STATUS_OBJECT_NAME_COLLISION
> > [2019/11/22 14:31:25.121995,  3] 
> > ../source3/lib/util.c:313(unix_clean_name)
> >   unix_clean_name [x64/3/DriverInstall_Pre_Vista_1]
> > [2019/11/22 14:31:25.122250,  3] 
> > ../source3/lib/util.c:313(unix_clean_name)
> >   unix_clean_name 
> > 
> [x64/{B764A331-6585-4FE6-8C6E-965E027AC30C}/DriverInstall_Pre_Vista_1]
> > [2019/11/22 14:31:25.122414,  0] 
> > 
> ../source3/printing/nt_printing.c:1145(move_driver_file_to_dow
> nload_area)
> >   move_driver_file_to_download_area: Unable to rename 
> > 
> [x64/{B764A331-6585-4FE6-8C6E-965E027AC30C}/driverinstall_pre_
> vista_1] 
> > to [x64/3/DriverInstall_Pre_Vista_1]: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
> > [2019/11/22 14:31:25.124344,  0] 
> > 
> ../source3/rpc_server/spoolss/srv_spoolss_nt.c:8612(_spoolss_A
> ddPrinterDriverEx)
> >   _spoolss_AddPrinterDriverEx: move_driver_to_download_area 
> failed - 
> > WERR_ACCESS_DENIED
> > [2019/11/22 14:31:25.126246,  2] 
> > ../source3/rpc_server/rpc_server.c:534(named_pipe_packet_process)
> >   Fatal error(NT_STATUS_CONNECTION_DISCONNECTED). Terminating 
> > client(172.17.172.10) connection!
> >
> >
> >
> > It seems that it tries to recreate /var/lib/samba/printers/x64/3 
> > although it allready exists
> 
> Doing this in CLI via rpclient does exactly the same thing:
> 
> 
> 
> rpcclient $>  adddriver "Windows x64" 
> xrxC8030:cupsdrvr.dll:xrxC8030.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
> result was WERR_ACCESS_DENIED
> 
> 
> ==> log.spoolssd.9 <==
> [2019/11/22 15:00:55.917157,  3] 
> ../source3/rpc_server/srv_pipe.c:1528(api_rpcTNP)
>    api_rpcTNP: rpc command: SPOOLSS_ADDPRINTERDRIVER
> [2019/11/22 15:00:55.917634,  3] 
> ../source3/smbd/vfs.c:113(vfs_init_default)
>    Initialising default vfs hooks
> [2019/11/22 15:00:55.917776,  3] 
> ../source3/smbd/vfs.c:139(vfs_init_custom)
>    Initialising custom vfs hooks from [/[Default VFS]/]
> [2019/11/22 15:00:55.917960,  3] 
> ../source3/smbd/vfs.c:139(vfs_init_custom)
>    Initialising custom vfs hooks from [acl_xattr]
> [2019/11/22 15:00:55.918310,  2] 
> ../source3/modules/vfs_acl_xattr.c:236(connect_acl_xattr)
>    connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = 
> true' and 'force unknown acl user = true' for service print$
> [2019/11/22 15:00:55.918743,  3] 
> ../source3/lib/util.c:313(unix_clean_name)
>    unix_clean_name [x64/3]
> [2019/11/22 15:00:55.918971,  2] 
> ../source3/smbd/open.c:3987(open_directory)
>    open_directory: unable to create x64/3. Error was 
> NT_STATUS_OBJECT_NAME_COLLISION
> [2019/11/22 15:00:55.919133,  3] 
> ../source3/lib/util.c:313(unix_clean_name)
>    unix_clean_name [x64/3/cupsdrvr.dll]
> [2019/11/22 15:00:55.919462,  3] 
> ../source3/lib/util.c:313(unix_clean_name)
>    unix_clean_name [x64/cupsdrvr.dll]
> [2019/11/22 15:00:55.919717,  0] 
> ../source3/printing/nt_printing.c:1145(move_driver_file_to_dow
> nload_area)
>    move_driver_file_to_download_area: Unable to rename 
> [x64/cupsdrvr.dll] to [x64/3/cupsdrvr.dll]: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
> [2019/11/22 15:00:55.920019,  0] 
> ../source3/rpc_server/spoolss/srv_spoolss_nt.c:8612(_spoolss_A
> ddPrinterDriverEx)
>    _spoolss_AddPrinterDriverEx: move_driver_to_download_area failed - 
> WERR_ACCESS_DENIED
> 
> 
> It seems you allready  had exactly this problem: 
> https://lists.samba.org/archive/samba/2019-April/222366.html
> 
> I thought it would be possible to do it direclyt from CLI/rpcclient
> 
> Do you know if there is any other way to make those drivers 
> work even if 
> we can't upload them through MMC ?
> 
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
> 




More information about the samba-technical mailing list