similar to: Kyocera 680 KX and driver uploads failing - anybody have success?

First of all, I forgot to mention, that I have Debian 9 with standard Samba 4.5. Modifying the oemsetup.inf should not be neccessary as I have set the os_major/minor to 6/0. The generic driver which comes with Windows is a Type 4 which should not be supported by samba as far as I read. I tried the van-belle driver. Same situation. I have found samba 4.8 for stretch at http://apt.van-belle.nl.

Hello, I am trying to install the driver on my print server. I used https://wiki.samba.org/index.php/Setting_up_Automatic_Printer_Driver_Downloads_for_Windows_Clients as a guide. I tried to install - KX driver, 32 and/or 64 bit - KX-XPS driver, 32 and/or 64 bit - Of both drivers the 64bit variants the installed driver package from system32 directory With all drivers I get the message

I'm a little disappointed with this printer. Technically, it seems fine. Printing from Mac OS X and Linux is effortless - Mac OS X prints through Samba -> CUPS or even direct to CUPS. But Windows... aarrgh! I've gone through the process of setting up the Point and Print drivers, but I can never get the Windows XP client to believe that it's actually installed the drivers.

As you did see on the download location. http://downloads.van-belle.nl/samba4/Patches/debian-S12761-s3-printing-Change-to-GUID-dir-if-we-deal-with-COPY.patch Is a working fix. I've used that in lots of samba versions. But i dont need the patch anymore, so i removed it from the builds. You can try : https://downloads.van-belle.nl/samba4/Kyocera/ Which is a customized driver made for me

Actually at van-belle it is 4.6.7 (or 4.6.9) for stretch. On Mon, Sep 17, 2018 at 06:50:38PM +0200, Matthias via samba wrote: > First of all, I forgot to mention, that I have Debian 9 with standard > Samba 4.5. > > Modifying the oemsetup.inf should not be neccessary as I have set the > os_major/minor to 6/0. > > The generic driver which comes with Windows is a Type 4 which

Hi, I'm working on a minimal print server setup for Windows 10/11 x64 clients. No domain, no Kerberos, no LDAP, only a few local users on a standalone server with some shared CUPS printers. Printing works well. After setting 'spoolss: os_major = 6' and 'spoolss: os_minor = 1' The *Kyocera KX Universal Driver* has uploaded well. But, that's all. No success uploading

Hello, I have a problem with the point'n'print driver installation. I followed the instructions on https://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id2626650 Now if I try to print on the Windows client I get an error 0x00000006. Here is my configuration. Printer: Kyocera FS-C2026MFP+ Server: Debian Squeeze, Samba version 3.5.6, CUPS cersion 1.4.4 Client:

Hello, I have a Kyocera FS1920 network printer, and I run an up-to-date CentOS 5.6 x86_64 workstation. When I try to print with evince or Firefox the default paper size is always set to US Letter whereas the printer use A4. I have searched and other people seem to have the problem, but the only recommendations that I have found boil down to setting the default paper size to A4 in the CUPS

Hallo, I'm running a Samba 2.2.5 server on a SuSE 8.1 box. I setup a [print$] share at server pslag, following the documentation. I have a [printer$] share too. Without it, Samba wouldn't export my cups printers for browsing. My config file is like that: [global] : printing = cups printcap name = CUPS printer admin = root load printers = Yes : [printers]

Hi all, I still have several problems with the printing system. The most critical is, that some drivers seem to cause an infinite RPC loop. I have a KYOCERA Mita KM 4230 KX driver installed. In this moment I can see SPOOLSS_GET_PRINTER and SPOOLSS_GET_PRINTERDATA requests and RPC responses on the net. Stracing the smbd process looks like this: ... pread(16,

I recently posted regarding problems configuring Samba. These have all been fixed but I am now struggling with the point and print facility. I have attempted to upload the drivers from Windows XP workstations but this seems to do nothing. So plan B was to manually copy the files to the appropriate print$ share folder, so far so good. The problem I now have is that the rpcclient utility simply

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

Hello, Environment: Samba-3.0.23c on Solaris 9 using LDAP (Sun DS 5.2) I'm trying to follow the procedure in the Samba 3 HOWTO in Chapter 21 to install printer drivers to the print$ share on the samba server. I've got as far as extracting the drivers from a Windows machine and am trying to register them with Samba using the rpcclient adddriver command. The command I'm using:

My W9x clients cannot download printer driver from samba 3.0.2rc1 with cups 1.1.17, while w2k clients do. The W9x clients open the Add Printer Wizard, connect to print$ share, request the ADOBEPS4.DRV file, but they stop at the beginning of the download. Permissions on print$\WINNT\0 directory are the same as print$\W32X86\2. cupsaddsmb was successful. I sniffed the packets while client was

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]

Waarschuwing: Er zijn 1 of meer bijlagen uit dit bericht verwijderd Waarschuwing: (KyUHCa.chm, KyUHlp.chm, KyUHPt.chm, KyUHDe.chm, KyUHFr.chm, KyUSNM.exe, KyUHSe.chm, KyoClassicUniversalPCL5_v3.0_Samba_WHQL.zip, KyUHSp.chm). Waarschuwing: Lees de "Bazuin-en-Partners-Attachment-Warning.txt" bijlage voor meer informatie. Hai Franz and Achmin. Attached in this mail is a driver made by

[root at samba ~]# cupsaddsmb -U administrator -v hp4 Password for administrator required to access localhost via SAMBA: ********************* Running command: smbclient //localhost/print$ -N -A /tmp/075335545d5bf -c 'mkdir W32X86;put /tmp/07533554ccef1 W32X86/hp4.ppd;put /usr/share/cups/drivers/ps5ui.dll W32X86/ps5ui.dll;put /usr/share/cups/drivers/pscript.hlp W32X86/pscript.hlp;put

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:

Dear Samba-experts, I'm trying to setup automatic printer download with our samba 4.19.4 fileserver which is a domain member of our samba 4.18.2 AD. printer drivers have been installed on the fileserver: root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c enumdrivers [Windows x64] Printer Driver Info 1: Driver Name: [Kyocera TASKalfa 5052ci NAEV] CUPS-printers have been installed

Hello, (please excuse poor translations of german Windows-GUI-items) a customer of ours has a strange problem trying to install a printer driver on the print$ share. The driver in question comes from http://www.kyocera.de/kyocera_n/german/downloads/downloads.html -> choose 'Treiber' -> choose 'Produkt Typ: Drucker', choose 'Produkt: FS-6020', choose 'Sprache: