similar to: Windows 2019 DC and samba dc

On 12.02.2019 11:16, Rowland Penny via samba wrote: > On Tue, 12 Feb 2019 14:28:44 +0500 > Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > >> I joined the windows 2019 domain, where among the controllers there >> is a Samba DC version 4.8.5, and after that the replica stopped >> working windows servers <--> samba DC. Upgrading to

On Tue, 12 Feb 2019 12:21:29 +0100 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > On 12.02.2019 11:16, Rowland Penny via samba wrote: > > On Tue, 12 Feb 2019 14:28:44 +0500 > > Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > > > >> I joined the windows 2019 domain, where among the controllers there >

Hello, I upgrade the schema for our main ADDC and everything works properly, but the member DC (DC to an Existing AD) fails. Both servers are in version 4.10.2 Distro: Debian 9.8 *Main ADDC:* [2019/04/16 15:43:03.814846, 0] ../../source4/rpc_server/drsuapi/getncchanges.c:2919(dcesrv_drsuapi_DsGetNCChanges) ../../source4/rpc_server/drsuapi/getncchanges.c:2919: DsGetNCChanges 2nd replication

On Tue, 12 Feb 2019 14:28:44 +0500 Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > I joined the windows 2019 domain, where among the controllers there > is a Samba DC version 4.8.5, and after that the replica stopped > working windows servers <--> samba DC. Upgrading to version 4.9.4 did > not help > > Errors: > > ``` > > фев 12

I have a very old domain i inherited that is running samba 4.5.6 but is on schema version 30. I added a windows 2003 DC and used the 2008r2 adprep.exe utility to upgrade the schema to version 47. To do so the 2003 server had to take the schema and infrastructure roles. I am now trying to use the repadmin utility to sync the schema back to samba to it is failing with the following: [2017/06/09

Thanks Rowland and Garming for your help!! How about "another DC", or 'a second DC' ? Ok. Got it! :D Alternatively, re-joining the domain controller (or joining a new DC and > demoting the old one) probably works because I believe there is code to > handle this case. I re-joined (remove secrets.tdb and .lbd, copy idmap from existing DC...) and now works properly!

Hello, Thanks for the feedback Garming!!! 👍 On Wed, Apr 17, 2019 at 12:35 AM Garming Sam <garming at catalyst.net.nz> wrote: > Hi, > > While I think we have most of the 2012 schema problems under control > now, there's still quite a bit of work to get the functional level > things working. In order to actually raise the level, we still need to > implement a number of

Hi, This is a known issue: https://bugzilla.samba.org/show_bug.cgi?id=12204 https://bugzilla.samba.org/show_bug.cgi?id=13713 There are currently patches in master to fix this issue. We could probably backport a patch to 4.10, but you'd have to rebuild Samba. Alternatively, re-joining the domain controller (or joining a new DC and demoting the old one) probably works because I believe there

Hi, While I think we have most of the 2012 schema problems under control now, there's still quite a bit of work to get the functional level things working. In order to actually raise the level, we still need to implement a number of features (mostly security). We're able to do some prep steps (so that things like Windows server 2012 R2 appear to join us but still use 2008 R2 FL) but

Hi, Everything seems to be ok, but the following is happening now. When I put a new computer in the domain, it only appears in the "second DC" and does not replicate to the first DC. root at dc3:~# samba-tool computer list |grep MINT-TESTE root at dc3:~# root at dc4:~# samba-tool computer list |grep MINT-TESTE MINT-TESTE$ root at dc4:~# Any idea? On Wed, Apr 17, 2019 at 8:12 AM

Hello, If when joining the computer in the domain and at the moment who received the request was the "second DC", it should automatically synchronize with the "first DC", correct? On Wed, Apr 17, 2019 at 5:00 PM Elias Pereira <empbilly at gmail.com> wrote: > Hi, > > Everything seems to be ok, but the following is happening now. > > When I put a new

Hello! Please look at this log entry: [2018/10/30 15:26:04.013132, 0] ../source3/param/loadparm.c:3358(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/share failed. Permission denied I don't know why this message is spamming my log, my version of samba is 4.9.1 from fedora 29, but problem existed long time ago with older versions. here is usershares

Hello, Rsync. --log-file-format="|%i|%B|%U|%G|%l|[%M]|// %n" After backup log to get this line: 2017/01/25 17:30:09 [8781] |hf |rw-r--r--|500|DEFAULT|83875|[2014/02/10-18:22:09]|// xml_error.txt groupID = DEFAULT The server looks like this: ls -lan | grep xml_error.txt -rw-r--r-- 1 500 1002 83875 Фев 10 2014 xml_error.txt groupID = 1002 The documentation is written:

Hi all, I have this application that lists videogames, which i am rewriting to follow REST. I need to have this url : /games/xbox360/halo-3 ( map.connect "/ games/:platform_id/:permalink",:controller => "games",:action => "show" ) This is no problem with map.connect, but with map.resources i can not make this. map.resources :games do |game|

I set up Passenger on manual - http://wiki.rubyonrails.org/deployment/apache-passenger Passenger and Apache install without errors. /etc/httpd/conf/httpd.conf: >> ... >> LoadModule passenger_module >> /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/ >> ext/apache2/mod_passenger.so >> PassengerRoot /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2 >>

I''ve made a model called Color to manage custom styles for my application. It works find when I''m running it locally in Mongrel, and I haven''t tried to deploy it yet. I use ZenTest and Autotest, and when I run autotest I''m getting the following message: "C:/rails/band/trunk/app/models/color.rb:1: Color is not a class (TypeError)" My Color model is

Hi, I'm experiencing a strange replication problem. Context: 5 samba DC in a single domain FSMO roles are owned by 10.0.10.11 (vs-dc-siege-001) vs-dc-siege-001: 10.0.10.11 vs-dc-siege-002: 10.0.10.12 vs-dc-vty-001: 10.0.100.11 vs-dc-vty-002: 10.0.100.12 vs-oc-vty-001: 10.0.100.156 I get the following errors in : samba-tool drs showrepl CN=Configuration,DC=corp,DC=mydomain,DC=fr

Hi all, I have 3 DCs running Samba 4.3.1 in the same domain. They seem to work quiet well with coherent databases on each of them. After rebuilding my RPM to include systemd units, I've joined a Samba 4.3.1 today, using --domain-critical-only. The join was successful, the replication was not. This DC has only 146 objects in the DB when it should have a bit less than 50000 objects. As I was

On Thu, Aug 15, 2024, 10:35 fransnicho <fransnicho at gmail.com> wrote: > Pada Rab, 14 Agu 2024 pukul 23.21 Rowland Penny via samba < > samba at lists.samba.org> menulis: > >> On Wed, 14 Aug 2024 16:58:12 +0700 >> fransnicho via samba <samba at lists.samba.org> wrote: >> >> > I can not join an additional new samba dc ver. 4.19.5 to an existing

On 16/11/15 15:09, mathias dufresne wrote: > That did not work. I've added DNS entries mentioned in that wiki page. I > also forced creation of all entries mentioned by samba_dnsupdate > --all-names --verbose. > So I expect all needed DNS entries are present. If some are still missing > they are not mentioned by samba_dnsupdate. And as samba_dnsupdate job is to > create