similar to: samba+cups printing. drivers on clients.

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've got some problems downloading Adobe PostScript printer drivers on a Windows 98 client : On the server side (Red Hat 9 / Samba 3.0.2 / Cups 1.1.17) : I installed succesfully my printers with Cups and they work fine on Linux I ran cupsaddsmb tool to copy the Adobe files in the [print$] directory which gives this result : in /etc/samba/W32X86/2 : cupsdrvr.dll cups.hlp

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

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.

Hi, I've tried unsuccessfully to get printing working under wine. I use wine version 20040309 on Debian unstable. I use cups for printing and it works without problems. According to the wine doc, I did not add any entries to the wine config file or to the registry. My printcap file looks like this: kyocera|Kyocera FS-1500:rm=sbs93:rp=kyocera: phaser|phaser:rm=sbs93:rp=phaser: When I

Hi All, Just a quick one. Some turkey has bought a kyocera 680 and we have to set it up for samba print sharing. We have about 35 other HP, Lexmark, and other things working a treat on this server so I know it's all working. When I try to upload the driver for the kyocera it uploads fine from my windoze box and everything looks sweet, I apply and I get the extra tabs as expected for

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, We're running samba-3.0.28a w/ cups-1.3.7 on debian etch to serve point and print to windows clients. http://us6.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#prt-modeset How do I check if a queue had the device mode set or not? thanks, Ryan

Ok you probely have hit : KB3163912 and KB3172985 problems. ( win 10 ) For win 7 you can have trouble due (KB3170455) Some good info here. http://blog.vectranetworks.com/blog/microsoft-windows-printer-wateringhole-attack Here are some tips to fix this also. - Remove the KB ( start with KB3172985) , but thats not my advice. - Setup the point and print restrictions as followed. Computer

While trying to debug the fact that printing works here but the print queue isn't returned properly, I found the following behaviour which might be a bug in Samba 1.9.18p10: I have (among others) the following lines in smb.conf: [printer1] create mode = 0700 read only = yes printable = yes path = /var/spool/samba printer name = %S comment = Kyocera

Hello people, and thanks for this list :) I have a problem with samba, but first let me tell you the overall thing. I want to migrate my win2k print server to a Samba3 one ;) My willing is to make this print server available for our domain users. Thus, I decided to use these global settings security = server server = myPDCServer My problem is that I can't make it work, all I get is an

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

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

We have a department using a DOS based application (written in C) within an MS window. By this I mean that the application is text based, and has no mouse capabilities at all. The application object code and its database all reside in a departmental share on our Samba instance on a Solaris box. We have about 30 people using the samba shares on this box at any time. The users have sent me an

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

I'm trying to share my HP 5610 on my Samba (3.0.24-1 fc6 x86_64) machine and am running into a typical HP related SANFU. The XP drivers supplied only install through the installation program. (ie. I can't use device manager to point XP to the driver and install it) So I installed the printer on my XP machine, used the installation program to install the drivers and then shared the

In an AD environment one may also sign an modified driver package https://technet.microsoft.com/en-us/library/eb9b35a3-64e9-4cd4-8393-9d8f5966f9c2 and deploy the certificate via an GPO https://technet.microsoft.com/de-de/library/cc770315(v=ws.10).aspx Am 07.06.2017 um 14:48 schrieb Achim Gottinger via samba: > Hello Franz, > > Out of curisoity I tried to install the old Kyocera

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

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