similar to: access DENIED for non-printserver bits

Ok, If it does not matter, tell me which printer driver version are you using. V3 or V4 that is one you should know, because if its a "V4" driver, then its not supported by samba. And samba doe only support non-packaged aware printer drivers. ( see wiki ) Are you using spoolss or spoolssd ? > Yes, I know WHERE it happens but not WHY... I need to know why so I can > do

Hi, Today I finally got time to do some more testing. I set up a Windows 10 machine but got the same problem (just wanted to make sure...). I will do more testing tomorrow but I have a question about an error I'm seeing in the logs. Do You know what "access DENIED for non-printserver bits" (log level 3) means? Regards, Åke --On 7 mars 2017 19:04:25 +0100 Marc Muehlfeld via samba

Hai, Can you tell me the brand and driver of the printer your trying , that helps. ( or send me a copy/link of the driver your installing ) I had a read thought your old(er) threat, but that didnt help. I did find the error in the following source code of samba. source3/rpc_server/srv_spoolss_nt.c but i cant help with that code much to complex for me, but at least you know is a "by

Hi Marc. > It sounds like the problem that came up last summer, after MS updated the Windows print spooler. > For details and how to fix it in a Samba AD, see: > > https://wiki.samba.org/index.php/Setting_up_Automatic_Printer_Driver_Downloads_for_Windows_Client > s#Creating_a_GPO_for_Trusting_the_Print_Server I have seen that but I guess it does not apppy in my situation

Hi all. We are running Samba 4.4.10 as an NT-domain server on Solaris 10. The server is also used to store printer preferences and drivers. We are using LDAP as the passdb backend. Now we need to change some printing preferences and change one printer driver, however I can not do any of those things any more (last time I did it we was running Samba 3.x...). When I log in to a Win 7 computer as

Ok,   > The "Access denied" happens before the installation would > have started. Ok so a mis configuration somewere. Since you not willing to share the smb.conf i?ll show you my part. this works as win xp upto win 10 32/64bit. ( tested with samba 4.4.x 4.5.x 4.6.x on debian jessie with cups and point and print setup.)   If anyone is questioning the ?acl_xattr:ignore

Hi Åke, Am 06.03.2017 um 15:02 schrieb Åke Holmlund via samba: > Now we need to change some printing preferences and change one printer > driver, however I can not do any of those things any more (last time > I did it we was running Samba 3.x...). > > When I log in to a Win 7 computer as a domain administrator but when I try > to add a new driver, using the Print Management

Hi. Ok - I took a shortcut: I finally found a 4.6.5 deb package for Ubuntu: https://launchpad.net/~rewi/+archive/ubuntu/samba I know that this package is just as fresh as bread from the oven, and that the packager states "not for production". Anyway, it installs without make, make install and configure, and there is no issues with paths. Wonderful :-) I can even install a printer on

Hi, Am 07.03.2017 um 12:55 schrieb Åke Holmlund via samba: >> It sounds like the problem that came up last summer, after MS updated >> the Windows print spooler. >> For details and how to fix it in a Samba AD, see: >> >> https://wiki.samba.org/index.php/Setting_up_Automatic_Printer_Driver_Downloads_for_Windows_Client >>

hi, I'm having trouble printing with smbclient via an embedded USB printserver. This printserver is a nifty little $35 box with an Ethernet jack and a USB jack that provides network access to your USB printer as a Windows share (a poor man's Jetdirect, if you will). I can connect to the printer with smbclient, but when I try to print anything, even a small text file, I always get the

Okay, I've got some progress now. Have fairly decent printserver working. I've been able to reproduce the same postive and negative results in two physical servers and now (finaly destination) a vmware server. What's working: ADS integration, this is a domain member Printer driver installation (for a few drivers) Printer installation / removal Printing. What's not working:

Hello, I've got an rh9 box which i am using for printing. I've got cups configured and my printer is working fine. Originally, i intended to use samba 2.2.x for printing, but then i saw that 3.0 was out so i installed it's rpm instead. My first of many questions, for printing to work correctly, samba and cups, what must be specified in terms of the printing line in smb.conf, bsd or

Running RH6.0 I am able to print just fine from linux, the problem now is getting smb printing working. I am using an Intel Netport Express PRO/100 printserver. Previous to my upgrade from RH5.2 when I had the printer directly connected to the samba server, I was able to print just fine from the windows client machines (not using the raw method) My /etc/printcap is as follows ##PRINTTOOL3##

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I like to move a Samba Printserver to a different machine. I would like to copy the printerdriver from the old to the new machine and not reinstall all drivers/printers again. When I only copy the files from /var/lib/samba/drivers to the new machine, there are no drivers listed on the new machine. How do I get the drivers listed on the new

Hi! I am new here. I am german. My system is a Centos 6.4 on a 2CoreCeleron. Its clones work on different Hardwares and processors. Centos 6.4 is great and very stable. I use it as CMS Webserver, FTP Server, Kolab suite incl. mailserver, Fileserver, Desktop, Skype all at the same time and it is working fine. Now i achieved to install a HP deskjet 1102 on Centos,

Hello, I have set up a Samba printserver at a school. The server is a standalone server, connected to no domain. I have installed printers with Cups, and uploaded Windows printerdrivers to the shared driver folder. I can add the shared printers in a Windows 10 Pro client, without any hassle. When I try the same in any Win 10 Home edition, I get Windows error messages like "error

Hello, we have a printserver with samba 3.4.3 and ADS. Every Friday morning, the server stops working and we get error messages. [2010/06/25 10:44:32, 1] smbd/sesssetup.c:342(reply_spnego_kerberos) Failed to verify incoming ticket with error NT_STATUS_LOGON_FAILURE! The only way to access the server again, is to login on the domain or the server. We have tried everything

I'm trying to configure a Linux workstation to print to my Samba printserver and can't figure out what I'm missing. Both are running CUPS. Windows clients print fine to the Samba box. Any ideas?

Hi I am using samba as a windows printserver with cups ,cupsaddsmb and the microsoft postscript driver. Now we have the first XP64 workstation in our network, and they are unable to download the 32 bit PS-Driver. How do I configure samba to serve the 64-bit drivers as well Greetings from Munich Hansj?rg

Hi all, I have set up two print servers with cups and samba 3.0.1. One of the samba servers is active and serves the windows clients. If the active server crashes (by hard- or software) I want to be able to make the other samba server active and act as the crashed samba server within minutes. Due to the fact that installing the windows printer drivers on samba takes a long time ( belonging to