similar to: Cannot use Print Server functions in NT4 style domain

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

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.

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

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

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

@Sonic # /etc/init.d/samba restart [ ok ] Restarting nmbd (via systemctl): nmbd.service. [ ok ] Restarting smbd (via systemctl): smbd.service. [ ok ] Restarting samba-ad-dc (via systemctl): samba-ad-dc.service. I may try rebooting as well, after trying @penny's fix. But that's what I've always been doing. When I use systemctl start nmbd smbd I get no output. On Sat, Apr 2, 2016 at

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> wrote: > On 02/04/16 17:37, Luke Barone wrote: > >> [global] >> server max protocol = SMB2 >> # Line above added by lbarone - March 30, 2016 >> name

[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 ports = 139 lock directory = /var/cache/samba preserve case =

OK, I'm rebooting the server now. Removed that line first. SELinux and App Armour are not installed on the servers. Tested with the firewall down (iptables), ulimit is not being reached, still lots of memory and hard drive space available... Since it's the weekend, no one else is in the building except for me. On Sat, Apr 2, 2016 at 10:20 AM, Rowland penny <rpenny at samba.org>

On 02/04/16 18:46, Luke Barone wrote: > 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 > <mailto:lukebarone at gmail.com>> wrote: > > OK, I'm

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 problems setting up the printer drivers using samba. I use a fresh setup of Samba Version 4.11.4-SerNet-Debian-6.buster and followed * https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member * https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Print_Server * .../Setting_up_Automatic_Printer_Driver_Downloads_for_Windows_Clients Cups is the default debian setup with

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

Has anyone had any success installing windows printer drivers onto a leopard-hosted print$ share? If I use the Add Printer Wizard method, if copies the driver files to \ \SERVER\print$\W32X86 then fails with an "Operation cannot be completed." If I use the rpcclient method I get a WERR_INVALID_PARAM error. Using the Adobe Generic PostScript driver as an example.

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

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

OK, we're getting closer here I think. I repeated with -d 2 without much help. Here is -d 3, which may point us in the right direction. As I suspected, it seems to point to some corruption in the DNS still, perhaps? The key line seems to be here: Missing parent while attempting to apply records: No parent with GUID 60e25dda-6d35-4aab-bfa5-6137cb271e27 found for object remotely known as