similar to: Installing windows drivers into print$ on OS X 10.5 Leopard

I can't even get cupsaddsmb to work right. I followed the configuration instructions from the documentation, and my smb.conf matches what the cupsaddsmb man page says. I am getting extremely frustrated with this and not being able to allow clients to download drivers from Samba. With cupsaddsmb, this is the error I am receiving when it gets to this point, over and over: Running command:

Hello, when i send the SIGHUP signal to Samba, then Samba won't load the printers from CUPS. I need to shutdown Samba and start it again. Now when i'am running cupsaddsmb i got the following errors(this error occours in 3.5.x but not in 3.2.x): server-p:/# cupsaddsmb -H server-p -v edv01 edv02 edv03 Kennwort f?r root erforderlich, um ?ber SAMBA auf server-p zugreifen zu k?nnen:

I'm setting up cups printing with Samba 4.0.5. I downloaded both the windows drivers and the postscript drivers and put them into /usr/share/cups/drivers/. I configured cups through the web interface. Created a printer and printed a test page. I edited smb.conf and put in the necessary entries for cups printing: [global] ... load printers = yes

Hi, I'm trying to add a printer driver to samba 2.2.7, part of the RedHat 9 distro. I have all the associated files under print$/W32X86 (I verified that they were where I thought they were from samba's POV by looking via smbclient). Below is the output from a getdriver command issued to a W2K PDC to get the names of all the required files for the particular printer: [Windows NT x86]

As an update to fix the badlock vulnerability I applied some updates to our (RHEL5-based) samba printer server last night, taking it from version 0:3.5.10-0.109.el5_8 to 0:3.6.23-12.el5_11 (rpm package versions). After this change attempts to add printer drivers with cupsaddsmb produced errors of the form: Running command: rpcclient localhost -N -A /tmp/cupsc7GVnF -c 'adddriver

Hello all, I'm running Samba 3.5.5 on Debian 5, and following the documentation as closely as I can to install drivers using rpcclient. I first install the driver on a Windows 7 x65 workstation, then use rpcclient/smbclient to fetch the files. I then use smbclient to put those on the print$ share of the Samba server. So far, so good. Then I use rpcclient to add those files, and that

Dear list, I've upgraded my server from Etch to Lenny and now the printer (HP LaserJet 6P) does not work any more through Samba. Printing a testpage via http://server:631 works perfectly so I skip giving details about the CUPS setup. Also lpstat reports the printer working # lpstat -a HP_LaserJet_6P accepting requests I tried to rerun cupsaddsmb. The driver files are copied to the

Cups 1.2.7 Debian Etch with Samba 3.0.24 Clients: WinXP SP3 (with Firewall completely off for testing) When I define a printer specifically in smb.conf, they show up as shared printers in WinXP. But when I follow the normal way (see below) to load all from cups they don't. I followed mainly the latest SAMBA-HOWTO (chapter 21-22) The only error I see in log.smbd when accessing the

Hi ! I'm using samba-3.0RC3 as a PDC (for testing). I'm using the ldap backend. I created 1 user, 1 computer and some groups. I mapped the unix groups domainadmins to "Domain admins" with my_personnal_sid-512. I added my user to domainadmins. I set "admin users = @domainadmins" in my smb.conf, but I still do not have domain admin rights on workstations :( Any idea

Hi ! I'm desperately looking for an answer here... I've been fighting all week-end with samba-3.0 and there's still something I can't do... Basically: how can I add some of my users to the Domain admin group ? I use FreeBSD-5.1+samba3.0RC3. My group maps: Admins du domaine (S-1-5-21-xxxx-512) -> domainadmins Utilisa. du domaine (S-1-5-21-xxxx-513) -> domainusers Invites du

We're using Cups and Samba with Adobe Postscript Drivers to print from XP SP2 machines via our Solaris and Linux Domain Controllers. Everything has been working OK, but when I setup an a new printer (identical ppd file to another one), it doesn't download the drivers on XP when I add the printer. This is happening on two domain controllers in different offices. It gives the error when

OK, then here's the weird part. I have another server, hosting other files, lets my Windows 10 system connect. The main server won't though. They are both running Debian Jessie 8.3, and Samba 4.1.17-debian. Below is the /etc/samba/smb.conf file *that works with Windows 7 and 10*: [global] workgroup = SD57 netbios name = SAMBA server string = sss interfaces

On 02/04/16 17:37, Luke Barone wrote: > [global] > server max protocol = SMB2 > # Line above added by lbarone - March 30, 2016 > name resolve order = host wins lmhosts bcast > write list = @domainadmins > passwd chat = *new*password* %n\n *new*password* %n\n *updated* > admin users = machine,add,lbarone, at domainadmins > smb

Please don't flame me. I did attempt to search before posting this question (through Gmail), if there's a better way, please let me know! I followed this article for implementing a Samba PDC: http://www.howtoforge.com/samba_setup_ubuntu_5.10_p4 Question 1) The only accout that appears to be able to add an account onto the domain is the root account. There must be a way to change that

On 02/04/16 18:06, Luke Barone wrote: > OK, I've tried commenting the line out. Ran /etc/init.d/samba reload, > but no change. Should I try a full server reboot then? > > On Sat, Apr 2, 2016 at 9:51 AM, Rowland penny <rpenny at samba.org > <mailto:rpenny at samba.org>> wrote: > > On 02/04/16 17:37, Luke Barone wrote: > > [global] >

On 02/04/16 20:02, Luke Barone wrote: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE > > > On Sat, Apr 2, 2016 at 11:57 AM, Luke Barone

Hi all, After some config changes and reboots, I got the Samba server running properly for my client computers running Windows 7. My issue now is with Windows 10. I see threads relating to setting "max protocol = NT1", but this seems to break the Windows 7 clients (which are finally working again). Below is my smb.conf file (which works for Windows 7): [global] workgroup = JMC

I have 2 printer queues setup on my samba 3.0.6 NT4-style PDC. About a month ago, one of them stopped working due to an issue with CUPS. After restarting CUPS, printing to that share was giving Access Denied. From a windows box, I was able to add drivers and set default print settings as a domain administrator but I still couldn't print. I created a new printer share pointing at the same

OK, this is working with the Windows 7 clients now. Looks like it was just a reboot. Now I have an issue with the Windows 10 clients... I'll open a new thread about that... On Sat, Apr 2, 2016 at 10:31 AM, Luke Barone <lukebarone at gmail.com> wrote: > OK, I'm rebooting the server now. Removed that line first. > > SELinux and App Armour are not installed on the servers.

Hi list, I have an NT4-style domain controller running on Samba 4.2.14-debian (Debian Jessie) that is acting as a file server. I am reading through the documentation, and attempting to use it as a print server as well. I have added the share declarations that I believed I needed, and CUPS is working properly with a test printer. Below is my smb.conf file (some sections redacted): [global]