Hi,
I'm trying to upload printer drivers on a fresh samba installation
(version 4.9.4). I configured the settings accordingly to the wiki and
also followed the instructions for adding printer drivers. I am able to
read and write to the print$ share and to access the samba server via
the printer management console.
However when I try to upload an driver (and I tried different type 3
drivers) I see that the files are being copied but at the end I get an
error message "Driver cannot be installed. This Operation is
unsupported". This is happening on a Windows 10 and on a Server 2008 R2
machine.
Do you have any ideas how to solve this?
Regards
Bernhard
Mandi! Bernhard Dick via samba In chel di` si favelave...> Do you have any ideas how to solve this?Printer drivers are sometimes a total mess. Some drivers there's no way to load (for example, some samsung MFP). Some other load, but you have to do 2-5 try before they work. Some other load, but you have to install them on a windows box, and then smbclient/rpcclient them in samba (see samba docs, manual driver installation). Note that some load, but still does not work. Some other also have a plethora of CABs, and you have to expand (some of) them to have driver loaded. Try at first the simpliest driver, eg 'PCL5', not the 'UNIDRIVER' one, possibly getting the from drivers archives. Good luck. ;) -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/ Polo FVG - Via della Bontà , 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000 (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
Hi, Am 25.03.2019 um 14:12 schrieb Marco Gaiarin via samba:> [...] > Some drivers there's no way to load (for example, some samsung MFP). > Some other load, but you have to do 2-5 try before they work.I did now try many different drivers from different vendors none of them worked thus I think there is something else wrong. I then did some more tests, trying to find anything being wrong with help of the process monitor and activating some more logs on the windows machine. What I see now is that just at the beginning of the upload the following error is in within the PrintService log: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" /> <EventID>224</EventID> <Version>0</Version> <Level>2</Level> <Task>41</Task> <Opcode>12</Opcode> <Keywords>0x4000000000008000</Keywords> <TimeCreated SystemTime="2019-04-08T08:07:23.917908000Z" /> <EventRecordID>3</EventRecordID> <Correlation /> <Execution ProcessID="3680" ThreadID="13184" /> <Channel>Microsoft-Windows-PrintService/Operational</Channel> <Computer>MATDT023.DOMAIN</Computer> <Security UserID="S-1-5-21-3794950379-127977205-3672732359-3005" /> </System> - <UserData> - <RemotePackage xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events"> <Function>UploadPrinterDriverPackage</Function> <Error>0x32</Error> <Server>\\print0</Server> </RemotePackage> </UserData> </Event> Maybe that helps getting to the root cause of the problem?> Some other load, but you have to install them on a windows box, and > then smbclient/rpcclient them in samba (see samba docs, manual driver > installation). Note that some load, but still does not work.A minimal upload using rpcclient was possible, but in that case Client systems do not get the driver version and thus "think" the driver has to be installed again multiple times. Regards Bernhard