similar to: samba - cups rights problem

Here is my printer config: printing = lprng load printers = yes use client driver = yes printer admin = @edutec, root printcap name = /etc/printcap print command = lpr -U%U@%M -r -P%p -J'%J' %s lpq command = lpq -P%p lprm command = lprm -U%U@%M -P%p %j lppause command = /usr/sbin/lpc -U%U@%M hold %p %j lpresume command =/usr/sbin/lpc -U%U@%M release

All, I have the following in my smb.comf for printing commands... # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/samba browseable = no print ok = yes print command = /usr/bin/lpr -P%p -r %s lpq command = /usr/bin/lpq -P%p lprm command = /usr/bin/lprm -P%p %j

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

First of all, thanks to everyone who has helped me out so far resolving my samba problems! The latest has to do with LPRng and directory permissions. LPRng requires 0600 permissions on the spool directory, owner daemon group daemon. Whenever a user tries to print through SAMBA, they do not have write access to the spool directory, as teh job comes in user/group of the person who printed. Any

Hi. > [sample] > comment = "Free for all" > path = /storage/everyone > read only = No > create mask = 0777 > directory mask = 0777 > guest ok = Yes This worked right away - thanks! Still having trouble with the printers. I can browse the printers, but after running through the "Add printer" wizard the

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

Hi, We've been stuck with this problem for a while now and we believe I tried enough potential solutions to justify my posting here. We're using samba 3.0.14a in Sarge in order to allow printing from Windows workstations (The authentication works with AD+Kerberos+Winbind) to a set of shared printers. Printing works perfectly but we would like to allow users to have control over the jobs

I'm currently having a problem with the new released Samba 2.2.5: I cannot print anymore on my shared printer. What is strange is that It worked fine with samba 2.2.4, but now I got an access denied whenever I try to access the printer... /var/spool/lpd/samba is chmod 777 and the username is in the group lp Here is part of my smb.conf: [global] workgroup = HOME netbios name =

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, I just installed 2 Win2K sp4 workstations on an otherwise working Samba 2.2.8a network and 2 of the 3 printers are showing "Access denied". What's up with that? The other computers that are working just fine are Win98, XP and Win2K NOT sp4. Here is part of the global section: printing = bsd load printers = yes disable spoolss = yes printcap name

Hi, I have the problem, that from a Windows 2000 System (possibly from others to), a user can use a printershare with the guest account and I don't know why. Following my smb.conf: Samba config file created using SWAT # from 192.168.2.20 (192.168.2.20) # Date: 2004/11/20 14:26:14 # Global parameters [global] unix charset = ISO_8859-15 display charset = ISO_8859-15 workgroup = WG interfaces

Hi again, I changed from 3.4.5 to 3.3.10 after an AD upgrade to 2008R2 and prinitng is working mor ore less but it is incredibly sloooow. My server has no remarkable load so it is not due to hardware bottlenecks. Are there any ways to 'tune' 3.3.10 or any tricks to make it faster ? cheers ~christoph -- /* Christoph Beyer | Office: Building 2b / 23 *\ * DESY

We have been using CUPS to handle printing and have run into some "features" some of which a fresh install of the responsible server will probably fix. However there are some disparities between the documentation and our practical experience for which a clear statement would help others. The docs state when using CUPS the relevent lines of SMB.CONF should look like this: printing=cups

Hi, I?ve installed fedora core 2 with samba 3.0.X. The pc is a PDC and I?ve configured samba like I could see in this easy manual: http://www.osnews.com/story.php?news_id=6684 (before this, I write for each pc : adduser -g "group" -d /dev/null -s /dev/null netbiosname$ > smbpasswd -a -m netbiosname ) My domain admin group is called smbadmins. I only have two kind of

I know this question has been answered here a while back, but I have not been able to find the mailing with the posts on it. -----==========----- I have a redhat server that I am using as a file/print server for student use. I am using samba to help the users with Windows. The problem I have is that when using printing a user can submit a print job, and it prints fine, but cannot see the

I am using Slackware 10.2 (kernel 2.4.29) and Samba 3.0.21c for my print server. The client workstations are WinNT4. I have two printers on the linux server..an HP DeskJet 600 and an Okidata B4250. I can install and print to the HP from any of the workstations. I can install the Okidata just fine, but when I try to print from Word, Excell, or any application Dr. Watson comes to visit. I get

[global] workgroup = IIG netbios name = TUX server string = Samba Server interfaces = 192.168.0.10/24 update encrypted = Yes logon path = \\TUX\profile\%u logon drive = H: domain logons = Yes os level = 65 preferred master = Yes domain master = Yes wins server = 127.0.0.1 wins support = Yes

Following the "security = domain in Samba 2.x" document in the SWAT documentation page I do this: root@pc194-79:/usr/local/samba/bin# smbpasswd -j MDU -r pv-mdu-server1 -Ujohnm%xxxxxxxx Joined domain MDU. root@pc194-79:/usr/local/samba/bin# This is in [globals]: security = DOMAIN encrypt passwords = Yes password server = pv-mdu-server1 pv-mdu-server2 And now I start Samba via smbd

I've seen this issue asked about and asked about in the archives, unfortunately I can't seem to find a real solution only people's theories. The issue involves a 2.2.5 Samba server acting as a member print server in a Windows 2000 domain. I can add printers from the server to clients in the domain and then print. The issue comes when I try and view/manage the print queue from Windows.

Hello, I run a Samba 2.2.3a server with XP clients successfully. I am aware of the fact that XP restricts access to some of its users (local) in regards to some programs. I am unsure which programs these are but MSN Messenger might be one of them. I think I heard guest users are not allowed to use MSN Messenger under XP by default. Now I have trouble to get MSN Messenger to start under XP for