similar to: Trust relationship between different domains

Hai Elias,   NET USE \\10.10.1.7\IPC$ /user:campus\administrator pa$$wd Works! :) C:\>net use Novas conexões serão lembradas. Status       Local     Remoto                    Rede -------------------------------------------------------------------------------              E:        \\vboxsrv\D_DRIVE         VirtualBox Shared Folders OK                     \\10.10.1.7\IPC$         

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

While this should work, neither is this particularly harmful. ?Links to objects that don't exist are ignored at runtime. Andrew Bartlett On Tue, 2023-04-04 at 14:39 -0300, Elias Pereira via samba wrote: > hi, > > Any clue? > > On Mon, Apr 3, 2023 at 10:17?AM Elias Pereira <empbilly at gmail.com> wrote: > > > hi, > > > > I have this DC in aws to

The principle was not made any changes to occur this problem. We infra have dc3 and dc4 ADDC. root at dc3:/etc/samba# samba -V Version 4.7.7-Debian (van-blle apt) Result of gpupdate /force in a joined computer client: C:\>gpupdate /force > Updating Policy... > User policy could not be updated successfully. The following errors were > encountered: > The processing of Group Policy

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

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, I have this DC in aws to fulfill the authentication need of our moodle. # samba -V Version 4.17.7-Debian DNS with SAMBA_INTERNAL The replication of the users and groups happens correctly. Some errors in running samba_dnsupdate, but it is ok anyway. When I ran the command samba-tool dbcheck, I got the return below. # samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes

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

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!

Hi folks, I manage the AD with rsat and recently we had problems with the CN of some users that have accentuation. When checking the user configuration via samba-tool user edit <username> in the location where the CN should be readable, a hexadecimal or something of that type appears. E.g: Acentuação da Silva dn: CN=Acentuação da Silva,OU=TESTE,DC=teste,DC=intra objectClass: top

Hi Rowland, Could you tell me what the correct permissions are for the bind9 files? On Wed, Jan 3, 2024 at 5:46?PM Elias Pereira <empbilly at gmail.com> wrote: > The only 'problem' I can see is that the group is set to 'bind' instead >> of 'root', why is this ? > > If I'm not mistaken, I did it on the wiki, but maybe I needed an older >

On Wed, 17 Jan 2024 16:43:26 -0300 Elias Pereira <empbilly at gmail.com> wrote: > Okay. How do I know if the command really ran correctly? :D You ran: samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br -d10 and got an error message. If you run: samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br

On Thu, 2024-04-11 at 14:21 -0300, Elias Pereira wrote: > Hello?Andrew, > > 1. What is the explanation for the fact that when the log level is > set to 5 or 7, the NT_STATUS_IO_TIMEOUT error does not appear, but > when it is at the default log level, it does? I don't have an explanation for this, sorry. ?Have you looked into the 1.5 second queries, what is sending them and

Okay. How do I know if the command really ran correctly? :D On Wed, Jan 17, 2024 at 4:26?PM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Wed, 17 Jan 2024 16:14:48 -0300 > Elias Pereira <empbilly at gmail.com> wrote: > > > With --async-op does it run in the background? Is the output saved in > > a log? > > Just add it to however you ran

Hello, I had posted this in another topic, but because the problem is different, I decided to create a new topic. Conf: - Primary DC/pdc Emulator as DC3 - Second DC as DC4 After an upgrade from schema 45 to 69 in DCs, when adding a computer in the domain and if the domain to respond is DC4 the synchronization for DC3 is not done. I already did several tests that I already knew and also new

hi, After a "samba-tool drs showrepl" I saw that there had been an error in the replication of ForestDnsZones. I ran a "samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br -d10" and the error below occurred. ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed

Hello guys, Why did you upgrade the schema to '69' ? > > That is the schema from 2012R2 and is still marked as experimental. I do not know why I did this update. Maybe I thought I could use DC as 2012R2. <sad> Could you run : > samba-tool ldapcmp ldap://dc3 ldap://dc4 --filter=cn,CN,dc,DC > And compair that output? I made the comparison. It has a jumble of

hi, Still dealing with the error. In some posts on the internet, a user reported that he has more than 40k objects in samba and that's why the error occurs. When running the command "samba-tool dbcheck --cross-ncs --fix --yes" reports that it has "Checking 16529 objects (Checked 16529 objects (0 errors))". So it wouldn't be my case. Running "samba-tool drs

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