similar to: Upgrading Samba 3 to Samba 4 - Domain Controller unreachable

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

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

@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

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, > we're seeing more and more issues. > > Computers are logging in

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

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>

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 =

Think I should actively STOP that service? On Sat, Apr 2, 2016 at 11:18 AM, Sonic <sonicsmith at gmail.com> wrote: > On Sat, Apr 2, 2016 at 2:07 PM, Luke Barone <lukebarone at gmail.com> wrote: > > [ 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 > >

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

First, background information. We are a large (geographically local) organization with 50 sites, including our HQ. Each site has a Debian Server running Samba in NT-Domain Controller mode. Each site is independant of the next, but are all named <SITE>.example.com. The workstations are connected, and working fine in our sites with the single servers. We had a recent network upgrade that now

Hey Luke, thanks for the help!!! It's working now!!! God bless you and your family!! :D Remember that GPOs need to run as the context of either the computer or the > user. Computers typically do not have access to many folders on a file > server, even as "Everyone". That is why the NETLOGON folder works. > > If you're deploying as a USER configuration, then it

On Sat, Apr 2, 2016 at 2:07 PM, Luke Barone <lukebarone at gmail.com> wrote: > When I use systemctl start nmbd smbd I get no > output. Actually that's good - it means it worked - starting both nmbd and smbd. And it's the proper way to run these services (since you're using systemd).

On 02/04/16 19:21, Sonic wrote: > On Sat, Apr 2, 2016 at 2:07 PM, Luke Barone <lukebarone at gmail.com> wrote: >> When I use systemctl start nmbd smbd I get no >> output. > Actually that's good - it means it worked - starting both nmbd and > smbd. And it's the proper way to run these services (since you're > using systemd). Wrong On debian there is a

Hi Elias, > I thought it worked, but after I uninstalled the software that I deployed > via user scope, it did not reinstall. I selected the "Redeploy application" > option, but it also did not work. The user scope GPO are run with the privileges and access tokens of the logged on user, so the user have local admin rights for install and need access rights to the share you

Which GPO? Computer or User Configuration? Remember that GPOs need to run as the context of either the computer or the user. Computers typically do not have access to many folders on a file server, even as "Everyone". That is why the NETLOGON folder works. If you're deploying as a USER configuration, then it should run as the context of the user, meaning the Everyone permission

On Fri, 12 Jan 2018 09:21:42 -0800 Luke Barone <lukebarone at gmail.com> wrote: > As well as what share... Are you trying to access the \\*\netlogon or > \\*\sysvol shares of a PDC? > There wouldn't be a sysvol share on a PDC, or do you mean a DC ? Rowland