similar to: Windows 10 and Samba 4.1.17-debian (NT Domain)

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 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

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

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

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

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

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 <lukebarone at gmail.com> wrote: > OK, then here's the weird part. I have another

Hi, i have a small problem, i use CUPS - Raw printing, which works perfectly .. i thought.. When i , as Administrator ( or domain Admins ) print and want 5 copies there will be 5 copies. But when i do this as a Domain User, i get only 1 copy. Where am i missing something. Here's my printer config. ## PRINTING Section 1 !! Global Settings !! printing = cups load

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

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

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 19:17, Luke Barone wrote: > 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

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

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. > [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

I am attempting to get printing services for Windows 2000 clients working with Samba on a Red Hat 7.2 box. The problem is I can not cancel print jobs (either from a PC or the local smb client). File sharing, and printing other than this problem, work fine. Here is a listing of configuration and system info: 1) the samba packages installed, 2) output of "uname -a", 3) the

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] >

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.

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

On 01/04/16 21:20, Luke Barone wrote: > Anyone able to chime in? Suggestions on where to go? > > On Thu, Mar 31, 2016 at 11:21 AM, Luke Barone <lukebarone at gmail.com> wrote: > >> Hi all, >> >> I upgraded Samba 3 to 4 when doing a Debian Wheezy to Jessie upgrade over >> the last couple of weeks. Most things worked, but now that staff are back, >>