similar to: GPO infrastructure? -> 4.8.x to 4.9.x

Am 02.07.19 um 16:24 schrieb Stefan G. Weichinger via samba: > Am 02.07.19 um 16:09 schrieb Stefan G. Weichinger via samba: >> >> I get problems with group policies not applied ... seems an older >> problem surfacing now. >> >> Before I debug at current level I consider upgrading the 2 DCs from >> 4.8.12 (Debian Stretch) to 4.9.9 >> >> Anything

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: vrijdag 12 juli 2019 10:24 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] GPO infrastructure? -> 4.8.x to 4.9.x > > Am 10.07.19 um 08:40 schrieb Stefan G. Weichinger via samba: > > > more of this: > >

Good morning friends, I have the following structure: Centos 6.6 1) AD samba using .tgz package 2) using the proxy Sernet packages which use command: samba-tool domain join XXX.corp DC -U Administrator --realm = XXX.corp and set the squid via NTLM. Issues: 1) after the update I get the following messages in / var / log / messages: Aug 13 04:08:56 kernel samba: Out of memory: Kill process

Am 09.07.19 um 20:00 schrieb Stefan G. Weichinger via samba: > Maybe I have to rejoin, I renamed the windows server after the join, and > there was now matching DNS record then. > > And I see stuff like this: > > /var/log/samba# tail -f log.samba > ../source4/dsdb/dns/dns_update.c:353: Failed SPN update - with error > code 1 > [2019/07/09 19:16:32.921798, 0] >

I was too quick to send my previous email. It can't really be a problem of the package since I have, as mentioned, another system with the exact same setup and the exact same package versions and it all works there... On Sun, 23 Dec 2018 at 11:18, Viktor Trojanovic <viktor at troja.ch> wrote: > Yes, I tried running dbcheck (see first email), it showed 0 errors from > the start, I

All, I am running samba as an AD on a Debian buster: *ii python-samba 2:4.9.5+dfsg-5+deb10u1 armel Python bindings for Sambaii samba 2:4.9.5+dfsg-5+deb10u1 armel SMB/CIFS file, print, and login server for Unixii samba-common 2:4.9.5+dfsg-5+deb10u1 all common files used by both the Samba server and clientii

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

Good morning Rowland. Today there are 2 servers with Samba 4.1.19 1) Samba 4.1.19 compiled used for the control domain (AD) 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain join" to use the Squid authenticating via NTLM. Before I was as follows: 1) Samba 4.0.4 compiled AD 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain

good day Ali Bendriss, I followed exactly this tutorial to update the samba. Thank you, everyone I'll be honest as I have full knowledge about the Samba 4 will redo the structure thus have more work more on the other hand I'm sure I will not make a mistake that can generate me more trouble. Regards, Gabriel Franca > Em 14/08/2015, à(s) 09:39, Ali Bendriss <ali.bendriss at

Thanks, Rowland. I'll give it some thought. At this point, I may even go back to slackware or gentoo. It is a bit much learning all the new system tools (systemd, systemctl, firewalld, NetworkManager, etc.) while moving from a samba standalone configuration to AD/DC, DNS, Kerberos, all for the first time. I'm also considering calling Pantek.com - - - I've had some very good

Hello Rowland Talking to users at that time discovered the following: They remove the machine network cable, put the User and Password them the domain, after the windows open the desktop they connect the network cable back in the machine and get to work. If you do this procedure is giving User and wrong password! On the issue of time the 2 DC's station using ntp. I stopped the samba

>Hi, please don't use .local, you say that no apple devices will come >near, but what about an iphone ? and what about avahi ? >When you ran configure, you might as well just run it like this: ./configure >All the rest are defaults and you do not really need debug. >You only need to alter /etc/nsswitch.conf (yes that's the one) if you >want/need your users to log into

Then you might have hitted this bug. https://bugzilla.samba.org/show_bug.cgi?id=13969 Patch is to be tested atm. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: vrijdag 12 juli 2019 14:28 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] GPO

I wanted to follow up to the list in hopes it will help others with similar configuration. Per previous posts -- OS: CentOS 7.153 Samba: Version 4.1.17-SerNet-RedHat-11.el7 Samba provisioned to act as: AD DC following Samba Wiki: Samba AD DC HOWTO Samba Internal DNS daemon deployed. 1. Disable selinux. Unless you have a solid understanding of how to configure it for your environment, please

On 3/16/2018 10:07 AM, barış tombul via samba wrote: > same problem. > Never pass the 4.8 version. > > samba-tool dbcheck --cross-ncs --fix > Unable to determine the DomainSID, can not enforce uniqueness constraint on > local domainSIDs > > Searching for dsServiceName in rootDSE failed: operations error at > ../source4/dsdb/samdb/ldb_modules/rootdse.c:516 > Failed

Hi, i have the same problem. Inplace upgrade and i get the following error. Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD services : ..done Mar 23 13:46:50 orion2 systemd[1]: Stopped LSB: initscript for the SAMBA AD services. Mar 23

Hi, It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers. Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC) However, users cannot be authenticated. Samba is running but these ports are closed : netbios-ssn 139/tcp # NETBIOS session service

I followed the manual and got 3 problems 1. When i start samba i got error: ../dsdb/dns/dns_update.c:249: Failed DNS update - NT_STATUS_IO_TIMEOUT 2. When i join some computer bind9 doesent update the host in DNS. 3. When i start command /usr/local/samba/sbin/samba_dnsupdate --verbose shell sometimes back result sometimes not.'' -- -- Pozdrav Aleksandar

Am 12.01.2019 um 23:08 schrieb Rowland Penny via samba: > On Sat, 12 Jan 2019 22:04:50 +0100 > Anton Blau via samba <samba at lists.samba.org> wrote: > > Is this all you installed ? : > apt-get install samba > > If so try reading this: > > https://wiki.samba.org/index.php/Distribution-specific_Package_Installation > > Hello Rowland, thank you for your help.

Am 22.07.19 um 10:39 schrieb Stefan G. Weichinger via samba: > Am 20.07.19 um 11:54 schrieb Joachim Lindenberg via samba: >> I figured it out myself. The kerberos configuration on the old dc cobra was bad ? no clue why it worked at all until yesterday. >> >> After fixing it, testing with kinit, and restarting the dc processes it resumed replication. > > pls show how you