similar to: General question about sharing HP printers via Samba

Hi, I just updated my samba servers (debian wheezy, sernet samba4) from version 4.1.12-9 to 4.1.14-9 and suddenly all my hp printers produce errors instead of printing. Kyocera printers are still working. HP printers all use HP Universal drivers Version 5.9.0.18326 with snmp disabled. Errors occure from Windows Server 2003 32Bit and Windows 7 clients. Here's an level 1 log of what

look at this bug report https://bugzilla.samba.org/show_bug.cgi?id=10984 Louis >-----Oorspronkelijk bericht----- >Van: achim at ag-web.biz [mailto:samba-bounces at lists.samba.org] >Namens Achim Gottinger >Verzonden: dinsdag 6 januari 2015 9:56 >Aan: samba at lists.samba.org >Onderwerp: [Samba] Problem with HP printers after upgrade from >4.1.12-9 to 4.1.14-9 >

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

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

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

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

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

Hi Louis, Hi Achim, on windows 10 i removed the 3176493 which is on windows 7 / 8 3177725. It has no effect on restriction. Its always restricted. Sven -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von Achim Gottinger via samba Gesendet: Montag, 15. August 2016 18:39 An: samba at lists.samba.org Betreff: Re: [Samba] Windows 10 point and print

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]

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

Hai Sven, Start here : http://www.infoworld.com/article/3107306/microsoft-windows/microsoft-admits-to-distributing-windows-printing-bugs-in-kb-3177725-and-kb-3176493.html .. ms bug again.. > Verzonden: maandag 15 augustus 2016 15:05 > Aan: 'samba at lists.samba.org' > Onderwerp: Re: [Samba] Windows 10 point and print restriction > > Hi Louis, > > Thanks for

Our office has had a Brother MFC-8510DN for at least five years - no issues. As has been said below, you do have to download and install the driver but the process hasn't been problematic. Having said that, I haven't pushed the limit on it's capabilities, just done rather plain printing. ________________________________ From: CentOS <centos-bounces at centos.org> on behalf of

On Sat, 2020-06-27 at 18:17 -0400, Jay Hart wrote: > We currently have a Brother MFC-5490CN. Printer firmware is dated > June 1010. (yeah, 10 years old).??Few years ago the brother software > wouldn't work for printing under Fedora.??No problem, can print under > Windows 10.??Then it stopped scanning.??Could still print...under > Windows. > > Now, to fix the scanning

At Sat, 27 Jun 2020 22:09:47 -0500 CentOS mailing list <centos at centos.org> wrote: > > > > On 6/27/20 5:26 PM, Ron Loftin wrote: > > On Sat, 2020-06-27 at 18:17 -0400, Jay Hart wrote: > >> We currently have a Brother MFC-5490CN. Printer firmware is dated > >> June 1010. (yeah, 10 years old).????????Few years ago the brother software > >>

On Sat, 27 Jun 2020 17:33:39 -0400 Jay Hart wrote: > If you had to rate which printer brand works better with Linux (Fedora and > Centos), what would it be? Any Brother printer that I've ever had the misfortune to have to deal with either didn't work at all or if could be made to work, it didn't work for long. If it's a Brother, run away as fast as you can. They're

On Sat, 2020-06-27 at 15:44 -0600, Frank Cox wrote: > On Sat, 27 Jun 2020 17:33:39 -0400 > Jay Hart wrote: > > > > > If you had to rate which printer brand works better with Linux > > (Fedora and > > Centos), what would it be? > Any Brother printer that I've ever had the misfortune to have to deal > with either didn't work at all or if could be made

On 6/27/20 5:26 PM, Ron Loftin wrote: > On Sat, 2020-06-27 at 18:17 -0400, Jay Hart wrote: >> We currently have a Brother MFC-5490CN. Printer firmware is dated >> June 1010. (yeah, 10 years old).??Few years ago the brother software >> wouldn't work for printing under Fedora.??No problem, can print under >> Windows 10.??Then it stopped scanning.??Could still

We currently have a Brother MFC-5490CN. Printer firmware is dated June 1010. (yeah, 10 years old). Few years ago the brother software wouldn't work for printing under Fedora. No problem, can print under Windows 10. Then it stopped scanning. Could still print...under Windows. Now, to fix the scanning features working I installed updated drivers under Windows, now it scans like champ, but

Did the first test on two different servers both are running debian wheezy and packported samba packages. On the server still running 4.6.2 it worked without problems to add the first available printer driver (Brother-DCP116C). On the other server already running 4.6.3 it faile with the error you and marc described. So I downgraded this server to 4.6.2 but i still get the error. Am

Log if it works api_rpcTNP: rpc command: SPOOLSS_ADDPRINTERDRIVEREX [2017/04/28 12:17:02.416040, 3] ../source3/smbd/vfs.c:113(vfs_init_default) Initialising default vfs hooks [2017/04/28 12:17:02.416064, 3] ../source3/smbd/vfs.c:139(vfs_init_custom) Initialising custom vfs hooks from [/[Default VFS]/] [2017/04/28 12:17:02.416088, 3] ../source3/smbd/vfs.c:139(vfs_init_custom)