similar to: Odd behavior since upgrading to 4.9.6

----- On Apr 23, 2019, at 11:34 AM, samba samba at lists.samba.org wrote: > On Tue, 23 Apr 2019 11:11:21 -0500 (CDT) > Mike Ray via samba <samba at lists.samba.org> wrote: > >> About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, >> things are functioning. >> >> However, I have come across several strange behaviors and wandered if >>

On Tue, 23 Apr 2019 11:11:21 -0500 (CDT) Mike Ray via samba <samba at lists.samba.org> wrote: > About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, > things are functioning. > > However, I have come across several strange behaviors and wandered if > anyone else has noticed similar behavior on 4.9.6 or has any > suggestions of what might be occurring. >

All- I've got 3 DCs (version 4.9.6-12) that, prior to today, were running without issue (as best I could tell). Every night I run a few commands to monitor the status of the DCs/domain. I run: * dbcheck --cross-ncs * samba-tool drs kcc <other DCs> * samba-tool ldapcmp <local DC> <other DCs> (domain|configuration|schema|dnsdomain|dnsforest) * samba-tool drs showrepl These

Le 19/11/2018 à 12:33, Julien TEHERY via samba a écrit : > Le 19/11/2018 à 11:14, Marco Gaiarin via samba a écrit : >> Mandi! Julien TEHERY via samba >>    In chel di` si favelave... >> >>> Is there a good pratice when adding new remote DCs in terms of >>> replication >>> topology? >> I think you have to define a topology of the domain, using

Hi all, i've got initial setup on DC1 (4.0.1)... all working good and flawless Added additional geographically distributed controllers (DC2, DC3, DC4,DC5) with 4.0.5 - no problem. All PC's can connect to their own site/DC Transferred all FSMO's to DC2 - transferred successfully (with seize "error" bug) DC1 crashed badly.... during maintenance, SAMBA was

Thanks Rowland, I have removed from options, and amended the forwarders. [global] workgroup = <MYDOMAIN> realm = <MYDOMAIN>.CORP netbios name = <HOSTNAME> server role = active directory domain controller idmap_ldb:use rfc2307 = yes idmap config * : range = 3000-7999 ----------> If I remove the portion I get errors -> idmap

a quick read and one thing, the dc4, after the upgrade to 4.7, did you reindex the ad database? if im correct, samba-tool dbcheck — reindex i did read that from a list somewere, a responce of andrew. greetz Louis (mobile) Op 23 okt. 2017 om 20:47 heeft mj via samba <samba at lists.samba.org> het volgende geschreven: Hi, Back in the samba 4.1 days, we experienced a samba database

Hello All, I hope you can assist me, I'm running Bind DLZ with our Samba AD DC environment Bind: BIND 9.11.4-P2-RedHat-9.11.4-9.P2.el7 (Extended Support Version) Samba: Version 4.11.6-SerNet-RedHat-9.el7 OS: Red Hat Enterprise Linux Server release 7.7 (Maipo) My DNS queries seems to be hanging intermittently, taking anything from 1sec - 15sec or even timing out. I'm been monitoring the

Hai,   Now, differences is fine, but can you see if one of the 2 servers is correct, and for that it might be handy to share the output.   You can push the good DB to the other DC. ( a forced replication )   And i can understand why you upgrade ...  Did you see :    samba-tool domain schemaupgrade --help Usage: samba-tool domain schemaupgrade [options] Domain schema upgrading Options:   -h,

Hello, dc3 = principal DC dc4 = secondary DC I had this problem last month after updating samba to version 4.10.x. and also the schema from 45 to 69. But it looked like it had been corrected. Today I noticed that on dc4 there are computers that are not on dc3. I updated: 4.7.x to 4.8.x 4.8.x to 4.9.x and only after that I upgrade to 4.10.x version. When I run these commands: samba-tool

im on phone, had a quick small look at the dc3 output. is your time in sync, it looks like a 3 - 10 min different. gr. Louis Op 7 mei 2019, om 18:34, Elias Pereira <empbilly at gmail.com> schreef: Hello, dc3: http://pasted.co/6b703479 dc4: http://pasted.co/5068fc6e diff: http://pasted.co/025c3242 On Tue, May 7, 2019 at 12:08 PM L.P.H. van Belle via samba <samba at

Hi, Back in the samba 4.1 days, we experienced a samba database corruption: tombstones not being deleted from sam.lbd, ultimately resulting in a huge database, full root disk, samba crashing, we were completely down. We asked the great guys at sernet to help, they did super work, and managed to get us up and running again, including the addition of a fresh DC4. Currently on 4.5.15, we have

Try again with : samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST As in dc5.your.dns.domain.tld ... Whats the result.? If it fails, please tell os your: OS? Content of /etc/hosts /etc/resolv.conf /etc/nsswitch.conf /etc/samba/smb.conf > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mike > Ray via samba >

On 21/09/2020 15:23, Elias Pereira via samba wrote: >> The question has to be, why do you only have it on one DC ? > > I am also asking myself this question because the dc3 was the first one I > provisioned. > > Ok. Somehow this was removed. Would it be possible to recreate this entry > or the best thing to do is to change the roles to dc4 and provision another > DC

----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: > Try again with : > > samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST > As in dc5.your.dns.domain.tld ... > > Whats the result.? The failure is still present -- no change in the output of the command: # samba-tool ldapcmp dc3.domain.local dc5.domain.local DNSFOREST ERROR(ldb):

On 21/09/2020 15:00, Elias Pereira via samba wrote: > Another doubt is about this bydefaults entry. > The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles guy. > Does it work that way or is there something wrong there? Whilst there are a few attributes that do not replicate, all DN's should. > * Comparing [DOMAIN] context... > > * DN lists have different

Cordialement, Doe Corp <https://www.openevents.fr/> <https://www.facebook.com/OPENevents-172305449504004/> <https://twitter.com/SocOPENevents> <https://www.linkedin.com/company/openevents/> Julien Téhéry Ingénieur Systèmes & Réseaux | OPENevents 15 avenue de l'Europe 86170 Neuville de Poitou phone : +33 5 49 62 26 03 <tel:+33549622603> mail :

Hi, I created the model below, which returns me the following warning message: In sem.default(ram = ram, S = S, N = N, param.names = pars, var.names = vars, : Could not compute QR decomposition of Hessian. Optimization probably did not converge. ######### Model ######## mDPDF = data.frame(mj1,mj2,mj3,mj4,mj5,eL1,eL2,eL3,eL4,eL5,aC1,aC2,aC3,aC4,disR1,disR2,disR3,disR4,disR5,

On 12/02/2020 12:54, L.P.H. van Belle via samba wrote: > > >> Hello Louis, >> >> Thanks for your reply. >> >> For that dig command I get... >> >> >> root at dc3.mydomain.com ~ $ (screen) dig NS $(hostname -d) >> >> ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS mydomain.com >> ;; global options: +cmd

So if this is done, is edns configure also ? ? in resolv.conf add: options edns0 ? and, name.conf test these. ? ??????? //?The forwarded zone to the AD-DC DNS use these also. ????????//dnssec-must-be-secure?internal.domain.tld no; ????????//dnssec-must-be-secure 168.192.in-addr.arpa no; ????????// listen-on-v6 { ::1; };? // test what works best, if not all?ipv6 is disabled also?enable this